Skip to content

Fix CUDA context leak in with cuda.gpus[N]: context manager #605

Fix CUDA context leak in with cuda.gpus[N]: context manager

Fix CUDA context leak in with cuda.gpus[N]: context manager #605

Re-run triggered April 13, 2026 19:54
Status Failure
Total duration 5m 40s
Artifacts 23

ci-new.yaml

on: push
compute-matrix
5s
compute-matrix
should-skip
6s
should-skip
ci-vars
7s
ci-vars
pre-commit
17s
pre-commit
test-conda  /  compute-matrix
2s
test-conda / compute-matrix
test-simulator  /  compute-matrix
4s
test-simulator / compute-matrix
Matrix: build-linux-64
Matrix: build-linux-aarch64
Matrix: build-windows
Matrix: test-conda / tests
Matrix: test-simulator / test
coverage-report  /  compute-matrix
4s
coverage-report / compute-matrix
test-thirdparty-awkward  /  compute-matrix
4s
test-thirdparty-awkward / compute-matrix
test-thirdparty-cudf  /  compute-matrix
5s
test-thirdparty-cudf / compute-matrix
test-thirdparty-nvmath  /  compute-matrix
test-thirdparty-nvmath / compute-matrix
test-wheels-deps-wheels  /  compute-matrix
3s
test-wheels-deps-wheels / compute-matrix
Matrix: test-linux-64
Matrix: test-linux-aarch64
Matrix: test-windows
Matrix: coverage-report / test
Matrix: test-thirdparty-awkward / test
Matrix: test-thirdparty-cudf / test
Matrix: test-thirdparty-nvmath / test
Waiting for pending jobs
Matrix: test-wheels-deps-wheels / test
Check job status
2s
Check job status
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Test linux-64 / py3.13, 13.1.0, local, rtxpro6000
Process completed with exit code 1.
Test linux-64 / py3.13, 13.1.0, local, rtxpro6000
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 13.1.0, local, rtxpro6000
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Check job status
Process completed with exit code 1.
Test linux-64 / py3.13, 13.1.0, local, rtxpro6000
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. 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-thirdparty-awkward / 12.9.1, 3.12, amd64, ubuntu24.04, l4, latest-driver, numba@*, cuda-core@*
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@v2.4. 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/