Skip to content

Extend _tensor_elementwise_impl with binary functions part 3 #8860

Extend _tensor_elementwise_impl with binary functions part 3

Extend _tensor_elementwise_impl with binary functions part 3 #8860

Triggered via pull request March 18, 2026 17:58
Status Cancelled
Total duration 1h 20m 42s
Artifacts 18

conda-package.yml

on: pull_request
Matrix: Build
Matrix: Test
Matrix: Test
Matrix: Array API conformity
Matrix: Upload
Clean up anaconda packages
0s
Clean up anaconda packages
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 20 warnings
Build (3.12, windows-2022)
The job has exceeded the maximum execution time of 1h20m0s
Build (3.12, windows-2022)
The operation was canceled.
Build (3.13, ubuntu-22.04)
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 (3.10, ubuntu-22.04)
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 (3.11, ubuntu-22.04)
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 (3.12, ubuntu-22.04)
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 (3.14, ubuntu-22.04)
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 (3.14, windows-2022)
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 (3.14, windows-2022)
ERROR: 'conda activate "build"' exited with code 1.
Build (3.14, windows-2022)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
Build (3.13, windows-2022)
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 (3.13, windows-2022)
ERROR: 'conda activate "build"' exited with code 1.
Build (3.13, windows-2022)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
Build (3.11, windows-2022)
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 (3.11, windows-2022)
ERROR: 'conda activate "build"' exited with code 1.
Build (3.11, windows-2022)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
Build (3.10, windows-2022)
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 (3.10, windows-2022)
ERROR: 'conda activate "build"' exited with code 1.
Build (3.10, windows-2022)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
Build (3.12, windows-2022)
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 (3.12, windows-2022)
ERROR: 'conda activate "build"' exited with code 1.
Build (3.12, windows-2022)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.

Artifacts

Produced during runtime
Name Size Digest
dpnp Linux Python 3.10
14.9 MB
sha256:4b2cff283ed7670c34594e1044a84ad499541275d43dcd29336b4478959fde51
dpnp Linux Python 3.11
15.3 MB
sha256:17fd86aeb5be1a677d939156b9854d5e15449b4742da67d7513a10e3506e9c49
dpnp Linux Python 3.12
15.3 MB
sha256:80643896a6288efb49c4d4b1a55f1708d5af24d692942cc73fc9f1ea87b6edb7
dpnp Linux Python 3.13
15.3 MB
sha256:59f82e9b259bfaf1dbfdd10eb79c63cee6ac03b259d240472d167bf8d3e9c100
dpnp Linux Python 3.14
15.4 MB
sha256:1b5e94b1afd76d01a87bfd13749af13481a4b187666b8f486446d67e4c90c107
dpnp Linux Wheels Python 3.10
29.6 MB
sha256:66e7635b7305b9a6a7b3112159374dbb2616684c471828a0587ecdbae34112a9
dpnp Linux Wheels Python 3.11
29.7 MB
sha256:007824a30f26aa76c67a679d9c79568bdedd73fef7d6215167e092dcccdc7e47
dpnp Linux Wheels Python 3.12
29.8 MB
sha256:a348e7c07bb5dd9b38aa874c019fc692fd6042b5b73ac953c6a9dd79f7c76e42
dpnp Linux Wheels Python 3.13
29.7 MB
sha256:9820c24536ce09c87b321c4dbcb5ea7715518d1087766d0c797bbd92e44b3b79
dpnp Linux Wheels Python 3.14
29.7 MB
sha256:80a46eb824c3448eceb21d4dd3fd1aa6c14da272bffdc101735383f9a20cdcf5
dpnp Windows Python 3.10
13.5 MB
sha256:6fce672a2da782f9ddba7c857577ce13ad6737fd3d76cc195d8e5998f9b248f7
dpnp Windows Python 3.11
13.9 MB
sha256:cd0a37089c9facb424cb002f4d44ed3c56b2e449d2a3e1dfe0da049421f9693f
dpnp Windows Python 3.13
13.9 MB
sha256:7c4c73888c3019aaad3f354b920cf52b7bb61eaa02addf798be90e8e652a7f15
dpnp Windows Python 3.14
13.9 MB
sha256:5da5b86e40e3c039b60eb6b066970de2128cf46013aac890341743533044ced5
dpnp Windows Wheels Python 3.10
27.4 MB
sha256:e0ab8b8e90d15f4f5bece5986f8dceaf7e4722c6a1f6bd90223b2a2880bf40eb
dpnp Windows Wheels Python 3.11
27.5 MB
sha256:471efaa081df805df27014379868e539de7d8f7241472b56bcd914e102763444
dpnp Windows Wheels Python 3.13
27.5 MB
sha256:0db6f059ba73dc61858acc65855ad917452af4bedbfe1b01b2c44550fa8b1e5e
dpnp Windows Wheels Python 3.14
27.5 MB
sha256:4ab162617622dcc2aaf584a0449ed8922668be36923db27e99dbbab62f7d0bf1