Skip to content

Bump actions/download-artifact from 8.0.0 to 8.0.1 #6091

Bump actions/download-artifact from 8.0.0 to 8.0.1

Bump actions/download-artifact from 8.0.0 to 8.0.1 #6091

Triggered via pull request March 16, 2026 13:46
Status Cancelled
Total duration 1h 45m 32s
Artifacts 20

conda-package.yml

on: pull_request
Matrix: build_linux
Matrix: build_windows
Matrix: test_linux
Matrix: array-api-conformity
Matrix: test_examples_linux
Matrix: test_windows
Matrix: upload_linux
Matrix: upload_windows
Clean up anaconda packages
Clean up anaconda packages
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 46 warnings
test_windows (3.12, false, windows-latest)
The job has exceeded the maximum execution time of 1h0m0s
test_windows (3.12, false, windows-latest)
The operation was canceled.
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.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.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.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.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/
array-api-conformity (3.10, false, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mshick/add-pr-comment@b8f338c590a895d50bcbfa6c5859251edc8952fc. 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.12)
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)
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.13)
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)
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`.
build_windows (3.10)
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)
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.14)
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)
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.11)
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, false, windows-latest)
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, false, windows-latest)
ERROR: 'conda activate "test_dpctl"' exited with code 1.
test_windows (3.11, false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_dpctl You can list all discoverable environments with `conda info --envs`.
test_windows (3.11, false, windows-latest)
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, false, windows-latest)
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, false, windows-latest)
ERROR: 'conda activate "test_dpctl"' exited with code 1.
test_windows (3.13, false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_dpctl You can list all discoverable environments with `conda info --envs`.
test_windows (3.13, false, windows-latest)
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, false, windows-latest)
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, false, windows-latest)
ERROR: 'conda activate "test_dpctl"' exited with code 1.
test_windows (3.10, false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_dpctl You can list all discoverable environments with `conda info --envs`.
test_windows (3.10, false, windows-latest)
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, false, windows-latest)
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, false, windows-latest)
ERROR: 'conda activate "test_dpctl"' exited with code 1.
test_windows (3.14, false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_dpctl You can list all discoverable environments with `conda info --envs`.
test_windows (3.14, false, windows-latest)
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, false, windows-latest)
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, false, windows-latest)
ERROR: 'conda activate "test_dpctl"' exited with code 1.
test_windows (3.12, false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_dpctl You can list all discoverable environments with `conda info --envs`.
test_windows (3.12, false, windows-latest)
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
dpctl Linux Python 3.10
11.7 MB
sha256:37ff3fe1f997a01376f761056778986be631e11b4ce45ea1cc36cb59103dbaf9
dpctl Linux Python 3.11
12.1 MB
sha256:ec383ffe5cde3e67754f959aec375638082af4878986fd5647fe69bce74ecdfb
dpctl Linux Python 3.12
12 MB
sha256:b99a7499d39d197761bc6961397150c24fb337b28d47a085b9f330d6bf7c62e2
dpctl Linux Python 3.13
12 MB
sha256:4f08312c84d37d79f5ccbc068a3691b0e6626112fa6db5aa7dfc4d93a37c0ba3
dpctl Linux Python 3.14
12 MB
sha256:207240154258a8721de7b5951db8811f09bf8ec198c444b45cf62d6ba972e25f
dpctl Linux Wheels Python 3.10
25.1 MB
sha256:a8547f2a2e39021a2ddd67c98cb9f490ed6956bf41bfcc3179d351894d8886d6
dpctl Linux Wheels Python 3.11
25.1 MB
sha256:f8b2607e4ae680ab4e2f2496864055179490bf248baab375c516fff235d28d53
dpctl Linux Wheels Python 3.12
25.1 MB
sha256:e5d07b4941f8a716f9aa3e04655e98e832811585f3dcdf1519b6bd5a0c1bfb0d
dpctl Linux Wheels Python 3.13
25.2 MB
sha256:08577329f6a247d1b13ac82d3d2bad0c529367fedb7ce7d39f459c14f801cf33
dpctl Linux Wheels Python 3.14
25.2 MB
sha256:b2f611da76d54cec3c7785818da592158de3d8e171174b30021bb508ecadbee9
dpctl Windows Python 3.10
11.5 MB
sha256:68486df27ea894d0826a39945f81563847409df35851f31ff94142b9136ee16f
dpctl Windows Python 3.11
11.8 MB
sha256:b27e5ce012214d9a42995fa8f60c600f8b63b1598967544fc55d8c54a4aa05af
dpctl Windows Python 3.12
11.7 MB
sha256:ae99d9110605aa50f2ab13ef662b7acd2b219bd7737c5fff93aef28eb448e012
dpctl Windows Python 3.13
11.7 MB
sha256:4a8deef2fd809a70f341d60b289342634ec5f8e15b340d0b82459b73e9068624
dpctl Windows Python 3.14
11.8 MB
sha256:bb8243dcafe02214fabccfa969174d38a02b78dbcccf7123ae50c86cd000530b
dpctl Windows Wheels Python 3.10
25 MB
sha256:04e27663d74a91374d90d9e850939538f2c8ce0587ed6bb2aeb39bad3c0ec2fb
dpctl Windows Wheels Python 3.11
25 MB
sha256:b78d6a37c8d7d7d2c7849ce8649749bfa539c04460a761910836235edc6e588c
dpctl Windows Wheels Python 3.12
25.1 MB
sha256:30278e82af0d02cc488725400ea54717046b46eea35711bcac258daa9729789d
dpctl Windows Wheels Python 3.13
25.1 MB
sha256:87d20026aef4c0cecc50408e3b798f8b321025b6741e73f3b56b6a03d3574195
dpctl Windows Wheels Python 3.14
25.1 MB
sha256:5f7fc8a940c9812c4dd09872b00799e9eef40b883de32bbf4cf03757267b3b88