-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
⚠️ CI failed on Linux_nogil.pylatest_pip_nogil ⚠️ #23786
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 nogil segfault was already noticed in #23762 (comment).
This is not deterministic and we were not able to reproduce locally, not sure what to do about it ... |
CI is no longer failing! ✅Successful run on Jul 26, 2022 |
The last time this job failed was 7 days ago. Since then the test has been passing. |
The failure still happens from time to time e.g. July 15 and July 22 (clicking on "edited" in the top post) ... |
Looking a bit closer, it seems like all the failing builds have in common that the architecture is SkylakeX but that the scipy shipped openblas (quite old 3.3 for some reason) detect the architecture as Prescott. On the succesful builds, the detected architecture is Haswell. Maybe this is loosely related to #21361. Failing build
Succeeding build:
|
I'm closing this given #23994 is merged and colesbury/nogil-install#2 is fixed. The CI will open another issue if this happens again. |
CI is still failing on Linux_nogil.pylatest_pip_nogil (Jul 25, 2022)
The text was updated successfully, but these errors were encountered: