-
Notifications
You must be signed in to change notification settings - Fork 108
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
Set gram_schmidt tolerances in POD to 0 to never truncate pod modes #980
Conversation
@renefritze, here we have another failed build that has no hash for reproducing and very long error message. |
That actually looks like the log was cut. I'm making the hypothesis dir downloadable to better debug cases like this. The new push might just clear the error too though. |
@renefritze, I can't reproduce the failures locally. Can you? Also, why are there so many 'Trying example:' blocks? I still don't really understand the output. There are also two different 'reproduce_failure' decorators mentioned. Why? |
Even using the right docker image?
An "example" is one input state for the test function.
Cause it found multiple failures. |
Yes.
But why do I see the output for all these examples? Can this be turned of?
I would have assumed that it stops when it finds a failing example. Is the second one the 'reduced' version? |
I think you'll have to ask the library authors for this.
Haven't seen a setting that controls output, but I haven't looked for one.
You can make hypothesis stop after it found one though, but I don't think that's a good choice for CI. |
In |
94d0416
to
7e869c3
Compare
So after rebasing on master, the hypothesis failure is gone, but I suspect we will see it again at some point .. - @renefritze should this be merged with 7e869c3 still in it? |
Codecov Report
|
Yes. That doesn't hurt and can be useful in a future occurrence. |
Fixes #961.