As nvbench.main links to nvbench as INTERFACE only, it no longer cons… #343
pr.yml
on: push
Compute matrix
7s
Matrix: nvbench
Verify Dev Containers
/
Verify devcontainer files are up-to-date
14s
Matrix: Verify Dev Containers / verify-devcontainers
CI
3s
Annotations
64 errors and 23 warnings
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 17, clang++) / Build/Test amd64/llvm17 / Build/Test amd64/llvm17
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 17, clang++) / Build/Test amd64/llvm17 / Build/Test amd64/llvm17
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 17, clang++) / Build/Test amd64/llvm17 / Build/Test amd64/llvm17
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 18, clang++) / Build/Test amd64/llvm18 / Build/Test amd64/llvm18
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 18, clang++) / Build/Test amd64/llvm18 / Build/Test amd64/llvm18
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 18, clang++) / Build/Test amd64/llvm18 / Build/Test amd64/llvm18
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 15, clang++) / Build/Test amd64/llvm15 / Build/Test amd64/llvm15
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 15, clang++) / Build/Test amd64/llvm15 / Build/Test amd64/llvm15
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 15, clang++) / Build/Test amd64/llvm15 / Build/Test amd64/llvm15
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 16, clang++) / Build/Test amd64/llvm16 / Build/Test amd64/llvm16
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 16, clang++) / Build/Test amd64/llvm16 / Build/Test amd64/llvm16
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 16, clang++) / Build/Test amd64/llvm16 / Build/Test amd64/llvm16
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 13, g++) / Build/Test amd64/gcc13 / Build/Test amd64/gcc13
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 13, g++) / Build/Test amd64/gcc13 / Build/Test amd64/gcc13
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 13, g++) / Build/Test amd64/gcc13 / Build/Test amd64/gcc13
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 19, clang++) / Build/Test amd64/llvm19 / Build/Test amd64/llvm19
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 19, clang++) / Build/Test amd64/llvm19 / Build/Test amd64/llvm19
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 19, clang++) / Build/Test amd64/llvm19 / Build/Test amd64/llvm19
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
Process completed with exit code 1.
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-llvm / build and test linux (12.0, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
Process completed with exit code 1.
|
|
NVBench CUDA12.0-llvm / build and test linux (12.0, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-llvm / build and test linux (12.0, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
Process completed with exit code 1.
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu24.04, amd64, gcc, 14, g++) / Build/Test amd64/gcc14 / Build/Test amd64/gcc14
Process completed with exit code 1.
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu24.04, amd64, gcc, 14, g++) / Build/Test amd64/gcc14 / Build/Test amd64/gcc14
To replicate this failure locally, follow the steps below:
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu24.04, amd64, gcc, 14, g++) / Build/Test amd64/gcc14 / Build/Test amd64/gcc14
🛠️ CMake Configure NVBench - Failed (⬆️ click above for full log ⬆️)
|
|
CI
Process completed with exit code 1.
|
|
Compute matrix
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. 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/
|
|
Verify Dev Containers / Verify devcontainer files are up-to-date
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 17, clang++) / Build/Test amd64/llvm17 / Build/Test amd64/llvm17
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 18, clang++) / Build/Test amd64/llvm18 / Build/Test amd64/llvm18
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 15, clang++) / Build/Test amd64/llvm15 / Build/Test amd64/llvm15
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 16, clang++) / Build/Test amd64/llvm16 / Build/Test amd64/llvm16
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 9, g++) / Build/Test amd64/gcc9 / Build/Test amd64/gcc9
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 13, g++) / Build/Test amd64/gcc13 / Build/Test amd64/gcc13
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 7, g++) / Build/Test amd64/gcc7 / Build/Test amd64/gcc7
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu22.04, amd64, gcc, 11, g++) / Build/Test amd64/gcc11 / Build/Test amd64/gcc11
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu22.04, amd64, llvm, 19, clang++) / Build/Test amd64/llvm19 / Build/Test amd64/llvm19
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. 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/
|
|
NVBench CUDA12.9-llvm / build and test linux (12.9, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu22.04, amd64, gcc, 12, g++) / Build/Test amd64/gcc12 / Build/Test amd64/gcc12
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 8, g++) / Build/Test amd64/gcc8 / Build/Test amd64/gcc8
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
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. 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/
|
|
NVBench CUDA12.0-llvm / build and test linux (12.0, ubuntu20.04, amd64, llvm, 14, clang++) / Build/Test amd64/llvm14 / Build/Test amd64/llvm14
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. 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/
|
|
NVBench CUDA12.0-gcc / build and test linux (12.0, ubuntu20.04, amd64, gcc, 10, g++) / Build/Test amd64/gcc10 / Build/Test amd64/gcc10
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. 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/
|
|
NVBench CUDA12.9-gcc / build and test linux (12.9, ubuntu24.04, amd64, gcc, 14, g++) / Build/Test amd64/gcc14 / Build/Test amd64/gcc14
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. 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/
|