Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for unsafe_trunc returning arbitrary values #289

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

kimikage
Copy link
Collaborator

This is in preparation for fixing issue #288.
The actual modification will be done in a separate PR.

Copy link

codecov bot commented Apr 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.05%. Comparing base (4b797a0) to head (739f83e).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #289   +/-   ##
=======================================
  Coverage   97.05%   97.05%           
=======================================
  Files           7        7           
  Lines         782      782           
=======================================
  Hits          759      759           
  Misses         23       23           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@kimikage kimikage force-pushed the issue288_test branch 3 times, most recently from baceada to 26df4bf Compare April 27, 2024 04:23
@kimikage kimikage marked this pull request as draft April 27, 2024 04:50
@kimikage kimikage force-pushed the issue288_test branch 3 times, most recently from 0460bc7 to 307b750 Compare April 28, 2024 07:35
@kimikage kimikage changed the title Add test for undefined behavior of unsafe_trunc Add test for unsafe_trunc returning arbitrary values Apr 28, 2024
@kimikage kimikage force-pushed the issue288_test branch 6 times, most recently from 68c6fca to 9f8ca6b Compare April 28, 2024 08:44
@kimikage
Copy link
Collaborator Author

Fine, everything is broken except the nightly build!

In my defense, this was (potentially) broken before I changed it and would have been even more broken if I hadn't.

@kimikage kimikage marked this pull request as ready for review April 29, 2024 09:21
@kimikage kimikage merged commit 2604b5a into JuliaMath:master Apr 29, 2024
17 of 22 checks passed
@kimikage kimikage deleted the issue288_test branch April 29, 2024 09:22
@kimikage kimikage mentioned this pull request Apr 30, 2024
38 tasks
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request Apr 30, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request Apr 30, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 1, 2024
kimikage added a commit to kimikage/FixedPointNumbers.jl that referenced this pull request May 13, 2024
kimikage added a commit that referenced this pull request May 13, 2024
* Backport "Fix test for exponentially growing `promote_type` (#280)"

* fix tests on 1.7 (#253)

Co-authored-by: Johnny Chen <johnnychen94@hotmail.com>
Co-authored-by: kimikage <kimikage.ceo@gmail.com>

* Mark `test_broken` for conversion to `Float16`

* Backport "Add test for `unsafe_trunc` returning arbitrary values (#289)"

---------

Co-authored-by: Kristoffer Carlsson <kricarl@student.chalmers.se>
Co-authored-by: Johnny Chen <johnnychen94@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant