-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
TEST: 1.9.x + blas variants #223
Conversation
…nda-forge-pinning 2023.01.26.16.59.55
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Scipy 1.9.3I had gotten stuck in #199 and didn't get around to doing the analysis for the 1.9 series yet. Now picking this up again to have a reasonable chain record of the changes from here to 1.10. TL;DR: Improvements all aroundFrom 40 failures out of 110 runs for 1.8.1, we're now at 32 failures out of 96 CI runs (added CPython 3.11, no PyPy, distinguished avx512 absence/presence for openblas) Notable
The good news:
The bad news
Restrictions
Details
** sum of Segfaults (S), Failures (F), resp. Timeouts (T); out of a total of 96 CI combinations being tested (the openblas builds haven't actually been split into avx512 present/absent, but I inferred them from the others) Build logs: linux + mkl + avx512: 1 failure
linux + openblas + non-avx512: 1 failure
linux + aarch64 + openblas: 1 failure
windows + mkl + avx512: 1 failure
windows + openblas: 7 failures
osx + accelerate: 7 failures
osx + blis: 1 failure
|
Looks great, thanks! The picture gets slightly better with every release cycle it looks like. We're unlikely to do a 1.9.4 at this point, so let's close this PR and focus on 1.10x? |
I close them as new versions become available. Not planning to invest more time here, but I have a slight preference to leave this open while it's still somewhat relevant (e.g. the last two available versions; will close once we have 1.11). |
Not that 1.11 is here, let's close this one. |
Following the same scheme as #199, #172, #153 & #130. Should not be merged for the same reasons as #153.