Skip to content

Merge pull request #2037 from ericniebler/rename-to-throw-dependent-s… #12

Merge pull request #2037 from ericniebler/rename-to-throw-dependent-s…

Merge pull request #2037 from ericniebler/rename-to-throw-dependent-s… #12

Triggered via push April 21, 2026 22:35
Status Failure
Total duration 19m 30s
Artifacts 17

ci.cpu.yml

on: push
Matrix: build-cpu-macos
Matrix: build-cpu-windows
Matrix: build-cpu
CI (CPU) (MacOS)
0s
CI (CPU) (MacOS)
CI (CPU) (Windows)
29s
CI (CPU) (Windows)
CI (CPU)
CI (CPU)
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 19 warnings
macos-CPU (MacOS) (clang, Debug)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-CPU (MacOS) (clang, Release)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
CPU (gcc 14, Release, c++23)
Process completed with exit code 2.
CPU (gcc 14, Debug)
Process completed with exit code 2.
CPU (gcc 14, Release, ASAN)
Process completed with exit code 2.
CPU (gcc 12, Release, TSAN)
Process completed with exit code 2.
CPU (gcc 14, Debug, TSAN)
Process completed with exit code 2.
CPU (gcc 12, Debug)
Process completed with exit code 2.
CPU (gcc 14, Debug, ASAN)
Process completed with exit code 2.
CPU (gcc 14, Release, LEAK)
Process completed with exit code 2.
CPU (clang 16, Debug, TSAN)
Process completed with exit code 2.
CPU (clang 16, Release, ASAN)
Process completed with exit code 2.
CPU (clang 16, Debug, c++23)
Process completed with exit code 2.
CPU (clang 16, Release)
Process completed with exit code 2.
CPU (clang 22, Debug)
Process completed with exit code 2.
CPU (gcc 13, Debug)
Process completed with exit code 2.
CPU (clang 16, Debug)
Process completed with exit code 2.
CPU (clang 22, Release)
Process completed with exit code 2.
CPU (gcc 12, Release)
Process completed with exit code 2.
CPU (gcc 14, Release, c++23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 14, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 14, Release, ASAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 12, Release, TSAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 14, Debug, TSAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 12, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 14, Debug, ASAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 14, Release, LEAK)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 16, Debug, TSAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 16, Release, ASAN)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 16, Debug, c++23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 16, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 22, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 13, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 16, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (clang 22, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (gcc 12, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (Windows) (msvc, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CPU (Windows) (msvc, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
sccache-client-logs-Linux-gcc12-cuda12.9-amd64-24749971333-1-15072 Expired
1.19 KB
sha256:1fcf5575756124815a0a2f4f5ee641e0abed85119c4e1b27569d11757cef1c13
sccache-client-logs-Linux-gcc12-cuda12.9-amd64-24749971333-1-32633 Expired
1.19 KB
sha256:19a722fdd95e7a976caa4200197000b7b92d4175f79118c10b0e3b612de1e380
sccache-client-logs-Linux-gcc12-cuda12.9-amd64-24749971333-1-9778 Expired
1.19 KB
sha256:1fcf5575756124815a0a2f4f5ee641e0abed85119c4e1b27569d11757cef1c13
sccache-client-logs-Linux-gcc13-cuda12.9-amd64-24749971333-1-7685 Expired
1.19 KB
sha256:973bf5084fea7a2bd7f9a447dbbb1bd4221e8cb2318cd022a79d339fb519a6cf
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-17326 Expired
1.19 KB
sha256:e7918d2836e9acbf38dd95b8161c282f58d8eaa72ab765730160078cad86bc6c
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-18230 Expired
1.19 KB
sha256:7b8490b35f377f8fa1db41f1f1bf8e52d3a680c0f6e90d68b842bbcd293aae12
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-1838 Expired
1.19 KB
sha256:ebf6cb8898df6de2585b471e8fb8bcb832d99bddef41d4cfe9060dc47302d1f1
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-29334 Expired
1.19 KB
sha256:ebf6cb8898df6de2585b471e8fb8bcb832d99bddef41d4cfe9060dc47302d1f1
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-6508 Expired
1.19 KB
sha256:8aaad7c82fcb02d8b304be3904b42697e60efa11ab4010881d00a8f45c401592
sccache-client-logs-Linux-gcc14-cuda12.9-amd64-24749971333-1-919 Expired
1.19 KB
sha256:8aaad7c82fcb02d8b304be3904b42697e60efa11ab4010881d00a8f45c401592
sccache-client-logs-Linux-llvm16-cuda12.9-amd64-24749971333-1-17762 Expired
1.19 KB
sha256:e59ced8d80e0800cea0c692eee19320571a9aaaba0bd70bf51f3ebf572adf1bd
sccache-client-logs-Linux-llvm16-cuda12.9-amd64-24749971333-1-2161 Expired
1.19 KB
sha256:163e007a8bea0f598b09359b78e5cb0facd4bf285accafad1450ec6e1cc2da15
sccache-client-logs-Linux-llvm16-cuda12.9-amd64-24749971333-1-25136 Expired
1.19 KB
sha256:88cdd896e1d0145dc9d4f518fe6a8d21537482f976643ac546dc94c6d25abda7
sccache-client-logs-Linux-llvm16-cuda12.9-amd64-24749971333-1-27260 Expired
1.19 KB
sha256:f9009ec5cd58cfae4f358f991a34082717f6cec733c24ee71cf21c8a6cffe998
sccache-client-logs-Linux-llvm16-cuda12.9-amd64-24749971333-1-30152 Expired
1.19 KB
sha256:dee48f7a5e6c940f7578dcf8e0184973e8d7d51c499fa2bd51badc85e416110a
sccache-client-logs-Linux-llvm22-cuda13.2-amd64-24749971333-1-31225 Expired
1.19 KB
sha256:3369db24cd266886d9b15f9a0974ec6695b6c6cc137fd349bd80fec7acf23deb
sccache-client-logs-Linux-llvm22-cuda13.2-amd64-24749971333-1-3625 Expired
1.19 KB
sha256:7394314917ffe9e268eb5749f862ff5a419a95dc9f2bab7fe994c7f4721eba93