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 failurelinux + openblas + non-avx512: 1 failurelinux + aarch64 + openblas: 1 failurewindows + mkl + avx512: 1 failurewindows + openblas: 7 failuresosx + accelerate: 7 failuresosx + 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.