Skip to content
Conda package using conda-forge

chore: meta.yaml to accommodate numpy-base or numpy #271

Sign in to view logs

chore: meta.yaml to accommodate numpy-base or numpy

chore: meta.yaml to accommodate numpy-base or numpy #271

Triggered via pull request March 24, 2026 21:25
@jharlow-inteljharlow-intel
synchronize #105
task/numpy_base_toggle
Status Success
Total duration 11m 53s
Artifacts 10

conda-package-cf.yml

on: pull_request
Matrix: build_linux
Matrix: build_windows
Matrix: test_linux
Matrix: test_windows
Fit to window
Zoom out
Zoom in

Annotations

40 warnings
build_windows (3.12, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (3.12, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.12, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.12, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
build_windows (3.10, 2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (3.10, 2.2)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.10, 2.2)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.10, 2.2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
build_windows (3.13, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (3.13, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.13, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.13, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
build_windows (3.11, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (3.11, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.11, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.11, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
build_windows (3.14, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (3.14, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.14, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.14, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test_windows (3.13, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_windows (3.13, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.13, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_windows (3.13, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test_windows (3.14, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_windows (3.14, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.14, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_windows (3.14, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test_windows (3.10, 2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_windows (3.10, 2.2)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.10, 2.2)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_windows (3.10, 2.2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test_windows (3.12, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_windows (3.12, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.12, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_windows (3.12, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test_windows (3.11, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_windows (3.11, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.11, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_windows (3.11, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.

Artifacts

Produced during runtime
Name Size Digest
mkl_random Linux Python 3.10
373 KB
sha256:0b646f7a0c39aaa2d82d4c5cab994a642f8712b19a88868b5d68371474b881d8
mkl_random Linux Python 3.11
389 KB
sha256:392206d5b5ce1008c9b45fda9fd11eaee023f72bc242fe9d68c1a3d65193c8a1
mkl_random Linux Python 3.12
381 KB
sha256:0e3e47b1f0a1420afe25e6c4bdadca2e5f5fe614dd5b81c318d9cfb4ed26d5fa
mkl_random Linux Python 3.13
383 KB
sha256:048a461308c82b823ab2a4836580965765f15d287e4dce4bc746243608d5ece7
mkl_random Linux Python 3.14
388 KB
sha256:0d927bad32138244db0c950d658c898de177f25059d071359608d2a6e5ed1567
mkl_random Windows Python 3.10
301 KB
sha256:58953f3461df9f884cc6bc1ff18976212303af646f9dc034d67b5619ecf533d0
mkl_random Windows Python 3.11
320 KB
sha256:c208bcc8609510abe5b25d964806e4519bb09bd654fbecd79faf249de8a4f756
mkl_random Windows Python 3.12
306 KB
sha256:ed2822780d819f5d82339a9f3d33cef7a487710dbc25968ec3171d0fbc779d02
mkl_random Windows Python 3.13
310 KB
sha256:8a4f15cd6cba91528b1527b1f42882f40260181af287481ed3a141132605d924
mkl_random Windows Python 3.14
310 KB
sha256:ac701e19270de7da0bb1dfb5524a281efa1613d7a45355a40b2fbeb9bb918c74