-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
⚠️ CI failed on Ubuntu_Jammy_Jellyfish.pymin_conda_forge_openblas_ubuntu_2204 (last failure: Aug 30, 2024) ⚠️ #29674
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
Comments
The errors seem to be due to tolerance, For instance:
Seems reasonable to me to have a lower tolerance for float32 maybe? |
There were similar issues for FastICA in the past, but I can not tell if the root cause is similar. |
Honestly I am a bit of a loss about what is happening here, the tests started failing on See build logs The failure is deterministic and the results are the same so this is not due to global random seed. The fact that at the same time two other builds fail with the same error (scipy-dev #29675 and free-threaded #29599) is also weird, since there is not much in common between them: Python 3.9 and latest versions from conda-forge for this build and Python 3.12 + dev versions from pip for the others. |
Have the machines changed on the CI? |
I'm also at a loss, but the diff is in the order of 1e-5. So I wouldn't mind relaxing the tests, however, it's really odd. |
Yeah I think relaxing the tests is the most pragmatic thing to do.
I quickly tried to have a look, at least the Docker image has not been changed according to https://github.com/actions/runner-images?tab=readme-ov-file#faqs last passing log and first failing log. Both says:
|
CI is no longer failing! ✅Successful run on Aug 31, 2024 |
This has been fixed by #29746. |
Uh oh!
There was an error while loading. Please reload this page.
CI is still failing on Ubuntu_Jammy_Jellyfish.pymin_conda_forge_openblas_ubuntu_2204 (Aug 30, 2024)
The text was updated successfully, but these errors were encountered: