[MAINT] Change clang-format for pre-commit #342
ndgrigorianconda-package.yml
on: pull_request
Matrix: build_linux
Matrix: build_windows
Matrix: test_linux
Matrix: test_windows
Annotations
35 warnings
|
build_linux (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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_linux (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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_linux (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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_linux (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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_linux (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
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, styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.12)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.14)
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, styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.14)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.13)
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, styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.13)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.11)
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, styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.11)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.10)
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, styfle/cancel-workflow-action@3155a141048f8f89c06b4cdae32e7853e97536bc. 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)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.10)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
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"' exited with code 1.
|
|
test_windows (3.11, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test
You can list all discoverable environments with `conda info --envs`.
|
|
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"' exited with code 1.
|
|
test_windows (3.12, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test
You can list all discoverable environments with `conda info --envs`.
|
|
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"' exited with code 1.
|
|
test_windows (3.10, 2.2)
EnvironmentNameNotFound: Could not find conda environment: test
You can list all discoverable environments with `conda info --envs`.
|
|
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"' exited with code 1.
|
|
test_windows (3.13, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test
You can list all discoverable environments with `conda info --envs`.
|
|
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"' exited with code 1.
|
|
test_windows (3.14, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test
You can list all discoverable environments with `conda info --envs`.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
mkl_random Linux Python 3.10
|
344 KB |
sha256:3ca4a8ad5d540e1ed9da25a5e065e606cda784e305b55cef250d1051c6a854f4
|
|
|
mkl_random Linux Python 3.11
|
354 KB |
sha256:b4f5d8647cb0a5ca0fb30a0e1da389970b32991043ceae91a808a0846676dafb
|
|
|
mkl_random Linux Python 3.12
|
349 KB |
sha256:1e334a2d5890380e2c5b77f03c61bbea48810924ebc52984a509284d7a270ed9
|
|
|
mkl_random Linux Python 3.13
|
352 KB |
sha256:96f2142101e400a3eda986fbf960569b98fd7d95c4efa2fd118143fee0120509
|
|
|
mkl_random Linux Python 3.14
|
354 KB |
sha256:be94f3be1ad8768cdb5c184723c746e8b4dcc60367296bf63e9848a02544e3ad
|
|
|
mkl_random Windows Python 3.10
|
281 KB |
sha256:d5d68cc26f7073125bc10897025d4040ad5bb71f15436ed9261ff7b3da349967
|
|
|
mkl_random Windows Python 3.11
|
292 KB |
sha256:072383b7de9ba47d701ccfdd5717b194f76f47c74a3414f74646cbbd273a3dfc
|
|
|
mkl_random Windows Python 3.12
|
282 KB |
sha256:818214cbd08dfb322a244b0e59b3feb49d9cb7b4b3a99c9f2028d91ffdde9ea1
|
|
|
mkl_random Windows Python 3.13
|
280 KB |
sha256:56a32f85db415dd4ea2de05cf64c11b3a6384e69584ac7e697c4ec01d30d8f27
|
|
|
mkl_random Windows Python 3.14
|
279 KB |
sha256:4e8e3110bdfbb1c3105dd20283cd00d3b5b7cc1dc8beb190ae0a67dbf4ba0560
|
|