[demo] Force Build stage failure to reproduce gating-check bug #4256
copy-pr-bot[bot]ci.yml
on: push
Matrix: build-linux-64
Matrix: build-linux-aarch64
Matrix: build-windows
Test sdist linux-64
/
Test sdist builds
5m 23s
Test sdist win-64
/
Test sdist builds
5m 53s
Matrix: test-linux-64
Waiting for pending jobs
Matrix: test-linux-aarch64
Waiting for pending jobs
Matrix: test-windows
Waiting for pending jobs
Check job status
2s
Annotations
48 errors and 9 warnings
|
Build win-64, CUDA 13.3.0 / py3.10
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.10
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.14
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.14
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.11
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.11
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.12
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.12
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.15
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.15
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.14t
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.14t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.13
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.13
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.15t
Process completed with exit code 7.
|
|
Build win-64, CUDA 13.3.0 / py3.15t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.10
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.10
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.11
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.11
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.14t
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.14t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.10
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.10
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.15
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.15
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.15t
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.15t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.14
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.14
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.15
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.15
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.13
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.13
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.15t
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.15t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.14
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.14
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.12
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.12
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.12
Process completed with exit code 7.
|
|
Build linux-aarch64, CUDA 13.3.0 / py3.12
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.14t
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.14t
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.11
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.11
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build linux-64, CUDA 13.3.0 / py3.13
Process completed with exit code 7.
|
|
Build linux-64, CUDA 13.3.0 / py3.13
INTENTIONAL FAILURE for CI gating-check bug demo. See https://github.com/NVIDIA/cuda-python/issues/2208
|
|
Build win-64, CUDA 13.3.0 / py3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 win-64, CUDA 13.3.0 / py3.15t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 sdist win-64 / Test sdist builds
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|