-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
TST: new errors on linux-{aarch64,ppc64le} related to cdf with fft in TestLevyStable #19337
Comments
There are also |
(and using My
I did notice some weaknesses for So I guess I'm saying I can't reproduce locally just yet, but do have convenient access to the hardware if there's a more specific route to reproduction. |
Thanks for checking! Good to know you're not hitting it. It might also somehow be related to QEMU, see discussion in #19210. Though since we didn't observe it for several runs, and then all at once, I'm guessing either infrastructure or third party libs are at fault. Though it's possible of course - like Ralf was saying - that there are lurking bugs already, and perhaps we're just now starting to trigger them. |
This is fixed as of 1.12 from the POV of conda-forge, closing. |
I'm getting some new errors in conda-forge/scipy-feedstock#255, which are most likely triggered somehow by a third-party dependency, as I didn't see these failures on any recent runs, and there's no new scipy version to blame. It started today, as of a couple hours ago, going from all green (modulo some spurious timeouts), to all aarch/ppc64le runs finishing with the exact same set of test failures.
Coincidentally, all the failing tests raise the same RuntimeWarning:
While the logs talk about missed toleranced, I think the failures must be considered total, given that one side of the comparision is unexpectedly constant zero or one.
test failures incl. main error message
The text was updated successfully, but these errors were encountered: