Conversation
|
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15989660644. Examine the logs at this URL for more detail. |
c0c8ef7 to
6521a40
Compare
|
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 ( |
cc3e44a to
1f4c9f4
Compare
|
Hi! This is the friendly automated conda-forge-linting service. I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/17422904817. Examine the logs at this URL for more detail. |
1f4c9f4 to
25f05d5
Compare
|
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 ( |
e102b90 to
3e1ecbd
Compare
|
@isuruf, any idea why might be happening? Obvious candidates are recent changes in the compiler stack, but I wouldn't be able to tell how/why? |
|
That's the numpy-feedstock/recipe/build.sh Line 13 in 69b9a91 |
|
Trying to fix this in #375. |
…5.12.21.08.15.33 Other tools: - conda-build 25.11.1 - rattler-build 0.54.0 - rattler-build-conda-compat 1.4.10
3e1ecbd to
3bcb7a2
Compare
|
It's been a while... 😅 Update for numpy 2.3.5, new LAPACK, MKL, blis, recipe v1A lot has happened in the last year. The recipe was translated to v1, we've finally managed to move past LAPACK 3.9, unblocked MKL 2025 and blis 2.0, etc. More below. The summary: from 5/85 failures for 2.2.0, we're now at 16/120 failures, mainly emulation failures on linux + aarch64 + OpenBLAS fails and some issues with osx+freethreading (that have been solved in numpy 2.4). Notable
Restrictions
# there are some tests that cannot really work in emulation, see e.g. numpy/numpy#20445
{% set tests_to_skip = tests_to_skip + " or Test_ARM_Features" %} # [build_platform != target_platform]
{% set tests_to_skip = tests_to_skip + " or Test_POWER_Features" %} # [build_platform != target_platform]
# test_new_policy reruns part of test suite; including a CPU feature test that fails in emulation
{% set tests_to_skip = tests_to_skip + " or test_new_policy" %} # [build_platform != target_platform]Details
** sum of Segfaults (S), Failures (F), resp. Timeouts (T); out of a total of 120 CI combinations being tested Build logs: osx + py314: 1 test failurelinux + aarch64 + openblas: 17 test failures |
Continuing the analysis from #341, #326, #317, #307, #293, #288, #273, #252, #237, #227 & #196. Do not merge.
(5 years of BLAS variant testing 😱...)