-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
possible intermittent failure in lapack test #24155
Comments
Those stack traces. It is not possible to see which test failed. |
@KristofferC, can we de-tersen the stack traces in some of these cases? Or is this lack of stack trace output not related to recent filtering changes? |
This should have nothing to do with the stacktrace filtering. I can try it of course. |
This is without filtering (by introducing a failure) when running
After:
A funny thing is that the file where the test failed ( |
#24181 should show the exact location of a failed |
Would be great if this issue could be updated with a new test failure that includes line information. |
Test Failed at /local/src/julia/test/linalg/lapack.jl:433 Awesome to now get the source location! @andreasnoack while you are on it, don't you think that these intermittent failures could be solved by using a more resilient test (like increasing |
Thanks for the location of the test error. I'm not sure increasing the tolerance is better. For some these test failures, the error could be arbitrary since the probability that a |
Isn't it possible then to generate a random matrix until it's non-singular? Also I don't understand "the bound is no too side too often"... But anyway it was just a suggestion as I'm not used to do testing of a functionality with always the same input value, but this is your call. Regarding |
Shall I fix this one with a fixed seed then? |
Should have been wide not side
👍
Yes, that would be great. |
Here: https://travis-ci.org/JuliaLang/julia/jobs/288008723
The text was updated successfully, but these errors were encountered: