-
Notifications
You must be signed in to change notification settings - Fork 0
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
it_always_has_the_normal_pointing_towards_the_first_body quickcheck failure #1
Comments
@arielb1 is this a consistent failure? if memory serves me right, this test has been known to cause failures from time to time. I have yet to find the time to address this problem, but if this test doesn’t fail consistently, it is unlikely to be related to the compiler but rather an unhandled edge case in my system. |
We did not attempt to run your program again. This looks like a fuzzer failure - your program was run with the arguments |
I managed to reproduce the issue on the latest stable Rust compiler:
The output closely matches the output in the issue, the discrepancy is likely due to floating point inaccuracies. So I would say yes, this is likely just an issue of a flaky test, nothing wrong with the compiler! |
OK. Then it's up to you to fix it (and meanwhile, we'll mark it so we won't get confused by it on the cargobomb blacklist). |
As a part of the cargobomb project, we have been testing your crate against both nightly and experimental versions of
rustc
. cargobomb is a project that runs experimental and nightly versions of the compiler against a large body of public rust code, in order to detect regressions and perform measurements.During one of these tests with an experimental compiler, a
quickcheck
test in your code had failed. That could have been caused by a bug in the experimental compiler, but it also might be caused by a problem in your code. The test report is available here.The test failure is as follows:
The text was updated successfully, but these errors were encountered: