Update cuda_core/cuda/core/__init__.py #2673
copy-pr-bot[bot]ci.yml
on: push
should-skip
5s
ci-vars
45s
Matrix: build-linux-64
Matrix: build-linux-aarch64
Matrix: build-windows
Matrix: test-linux-64
Matrix: test-linux-aarch64
Matrix: test-windows
Check job status
3s
Annotations
140 errors, 54 warnings, and 18 notices
|
Test linux-64 / py3.13, 12.9.1, wheels, v100
Process completed with exit code 4.
|
|
Test linux-64 / py3.13, 12.9.1, wheels, v100
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, 12.9.1, wheels, v100
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.
|
|
Test linux-64 / py3.10, 12.9.1, local, v100
Process completed with exit code 4.
|
|
Test linux-64 / py3.10, 12.9.1, local, v100
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.10, 12.9.1, local, v100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Docs / Build docs
Process completed with exit code 2.
|
|
Test linux-aarch64 / py3.10, 12.9.1, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.10, 12.9.1, local, a100
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-aarch64 / py3.10, 12.9.1, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.10, 13.2.0, wheels, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.10, 13.2.0, wheels, l4
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.10, 13.2.0, wheels, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-aarch64 / py3.10, 13.0.2, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.10, 13.0.2, wheels, a100
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-aarch64 / py3.10, 13.0.2, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-aarch64 / py3.10, 13.2.0, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.10, 13.2.0, wheels, a100
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-aarch64 / py3.10, 13.2.0, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.10, 13.0.2, wheels, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.10, 13.0.2, wheels, l4
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.10, 13.0.2, wheels, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.12, 12.9.1, local, l4
Process completed with exit code 255.
|
|
Test linux-64 / py3.12, 12.9.1, local, l4
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.12, 12.9.1, local, l4
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.
|
|
Test linux-64 / py3.12, 13.2.0, wheels, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.12, 13.2.0, wheels, l4
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.12, 13.2.0, wheels, l4
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.
|
|
Test linux-64 / py3.11, 13.2.0, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.11, 13.2.0, local, l4
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.11, 13.2.0, local, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.11, 12.9.1, wheels, rtxpro6000
Process completed with exit code 4.
|
|
Test linux-64 / py3.11, 12.9.1, wheels, 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.11, 12.9.1, wheels, rtxpro6000
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.11, 13.0.2, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.11, 13.0.2, local, l4
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.11, 13.0.2, local, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-64 / py3.12, 13.0.2, wheels, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.12, 13.0.2, wheels, l4
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.12, 13.0.2, wheels, l4
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.
|
|
Test linux-64 / py3.14, 13.2.0, local, t4(x2)
Process completed with exit code 4.
|
|
Test linux-64 / py3.14, 13.2.0, local, t4(x2)
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.14, 13.2.0, local, t4(x2)
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.
|
|
Test linux-aarch64 / py3.14t, 13.2.0, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14t, 13.2.0, local, a100
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-aarch64 / py3.14t, 13.2.0, local, a100
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.
|
|
Test linux-64 / py3.14t, 13.2.0, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14t, 13.2.0, local, l4
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.14t, 13.2.0, local, l4
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.
|
|
Test linux-64 / py3.13, 13.2.0, local, rtxpro6000
Process completed with exit code 4.
|
|
Test linux-64 / py3.13, 13.2.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.2.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.
|
|
Test linux-64 / py3.13, 13.2.0, local, h100
Process completed with exit code 4.
|
|
Test linux-64 / py3.13, 13.2.0, local, h100
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.2.0, local, h100
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.
|
|
Test linux-64 / py3.13, 13.0.2, local, rtxpro6000
Process completed with exit code 4.
|
|
Test linux-64 / py3.13, 13.0.2, 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.0.2, 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.
|
|
Test linux-64 / py3.13, 13.0.2, local, h100
Process completed with exit code 4.
|
|
Test linux-64 / py3.13, 13.0.2, local, h100
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.0.2, local, h100
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.
|
|
Test linux-64 / py3.14, 13.2.0, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14, 13.2.0, local, l4
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.14, 13.2.0, local, l4
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.
|
|
Test linux-64 / py3.14t, 13.0.2, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14t, 13.0.2, local, l4
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.14t, 13.0.2, local, l4
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.
|
|
Test linux-64 / py3.14t, 13.2.0, local, h100(x2)
Process completed with exit code 4.
|
|
Test linux-64 / py3.14t, 13.2.0, local, h100(x2)
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.14t, 13.2.0, local, h100(x2)
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.
|
|
Test linux-aarch64 / py3.11, 12.9.1, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.11, 12.9.1, wheels, a100
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-aarch64 / py3.11, 12.9.1, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-aarch64 / py3.12, 13.2.0, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.12, 13.2.0, wheels, a100
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-aarch64 / py3.12, 13.2.0, wheels, a100
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.
|
|
Test linux-aarch64 / py3.11, 13.0.2, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.11, 13.0.2, local, a100
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-aarch64 / py3.11, 13.0.2, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-aarch64 / py3.13, 12.9.1, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.13, 12.9.1, wheels, a100
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-aarch64 / py3.13, 12.9.1, wheels, a100
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.
|
|
Test linux-aarch64 / py3.12, 13.0.2, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.12, 13.0.2, wheels, a100
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-aarch64 / py3.12, 13.0.2, wheels, a100
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.
|
|
Test linux-64 / py3.14, 12.9.1, wheels, t4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14, 12.9.1, wheels, t4
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.14, 12.9.1, wheels, t4
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.
|
|
Test linux-aarch64 / py3.14, 13.0.2, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14, 13.0.2, local, a100
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-aarch64 / py3.14, 13.0.2, local, a100
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.
|
|
Test linux-64 / py3.14t, 12.9.1, local, t4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14t, 12.9.1, local, t4
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.14t, 12.9.1, local, t4
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.
|
|
Test linux-aarch64 / py3.12, 12.9.1, local, a100
Process completed with exit code 255.
|
|
Test linux-aarch64 / py3.12, 12.9.1, local, a100
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-aarch64 / py3.12, 12.9.1, local, a100
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.
|
|
Test linux-64 / py3.14, 13.0.2, local, l4
Process completed with exit code 4.
|
|
Test linux-64 / py3.14, 13.0.2, local, l4
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.14, 13.0.2, local, l4
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.
|
|
Test linux-aarch64 / py3.14t, 13.0.2, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14t, 13.0.2, wheels, a100
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-aarch64 / py3.14t, 13.0.2, wheels, a100
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.
|
|
Test linux-aarch64 / py3.14, 13.2.0, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14, 13.2.0, local, a100
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-aarch64 / py3.14, 13.2.0, local, a100
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.
|
|
Test linux-aarch64 / py3.11, 13.2.0, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.11, 13.2.0, local, a100
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-aarch64 / py3.11, 13.2.0, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
|
Test linux-aarch64 / py3.14, 12.9.1, wheels, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14, 12.9.1, wheels, a100
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-aarch64 / py3.14, 12.9.1, wheels, a100
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.
|
|
Test win-64 / py3.14, 12.9.1, wheels, v100 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.14t, 13.0.2, wheels, a100 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.12, 12.9.1, wheels, l4 (MCDM)
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.13, 13.0.2, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.13, 13.0.2, local, a100
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-aarch64 / py3.13, 13.0.2, local, a100
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.
|
|
Test win-64 / py3.10, 12.9.1, wheels, rtx2080 (WDDM)
Process completed with exit code 1.
|
|
Test linux-aarch64 / py3.14t, 12.9.1, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.14t, 12.9.1, local, a100
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-aarch64 / py3.14t, 12.9.1, local, a100
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.
|
|
Test win-64 / py3.14t, 13.2.0, wheels, a100 (MCDM)
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.13, 13.2.0, local, a100
Process completed with exit code 4.
|
|
Test linux-aarch64 / py3.13, 13.2.0, local, a100
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-aarch64 / py3.13, 13.2.0, local, a100
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.
|
|
Test win-64 / py3.11, 12.9.1, local, v100 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.14t, 12.9.1, local, l4 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.11, 13.2.0, wheels, rtx4090 (WDDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.11, 13.0.2, wheels, rtx4090 (WDDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.13, 12.9.1, local, l4 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.14, 13.2.0, local, l4 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.12, 13.0.2, local, a100 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.14, 13.0.2, local, l4 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.12, 13.2.0, local, a100 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.13, 13.0.2, wheels, rtxpro6000 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.13, 13.2.0, wheels, rtxpro6000 (MCDM)
Process completed with exit code 4.
|
|
Test win-64 / py3.10, 13.0.2, local, rtxpro6000 (TCC)
Process completed with exit code 4.
|
|
Test win-64 / py3.10, 13.2.0, local, rtxpro6000 (TCC)
Process completed with exit code 4.
|
|
Check job status
Process completed with exit code 1.
|
|
Build linux-64, CUDA 13.2.0 / py3.14
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.12
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64, CUDA 13.2.0 / py3.13
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.13
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64, CUDA 13.2.0 / py3.14t
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64, CUDA 13.2.0 / py3.11
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64, CUDA 13.2.0 / py3.12
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.11
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.10
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.14
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64, CUDA 13.2.0 / py3.10
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64, CUDA 13.2.0 / py3.14t
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, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 win-64, CUDA 13.2.0 / py3.10
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64 / py3.10, 12.9.1, local, v100
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/
|
|
Docs / Build docs
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, conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
Docs / Build docs
warning libmamba You are using 'pip' as an additional package manager.
Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
|
|
Build win-64, CUDA 13.2.0 / py3.11
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-aarch64 / py3.10, 12.9.1, local, a100
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/
|
|
Build win-64, CUDA 13.2.0 / py3.14
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 win-64, CUDA 13.2.0 / py3.13
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64 / py3.12, 12.9.1, local, l4
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/
|
|
Build win-64, CUDA 13.2.0 / py3.12
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64 / py3.11, 13.2.0, local, l4
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 linux-64 / py3.11, 13.0.2, local, l4
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 linux-64 / py3.14, 13.2.0, local, t4(x2)
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 linux-aarch64 / py3.14t, 13.2.0, local, a100
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 linux-64 / py3.14t, 13.2.0, local, l4
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 linux-64 / py3.13, 13.2.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 linux-64 / py3.13, 13.2.0, local, h100
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 linux-64 / py3.13, 13.0.2, 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 linux-64 / py3.13, 13.0.2, local, h100
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/
|
|
Build win-64, CUDA 13.2.0 / py3.14t
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, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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 linux-64 / py3.14, 13.2.0, local, l4
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 linux-64 / py3.14t, 13.0.2, local, l4
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 linux-64 / py3.14t, 13.2.0, local, h100(x2)
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 linux-aarch64 / py3.11, 13.0.2, local, a100
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 linux-aarch64 / py3.14, 13.0.2, local, a100
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 linux-64 / py3.14t, 12.9.1, local, t4
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 linux-aarch64 / py3.12, 12.9.1, local, a100
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 linux-64 / py3.14, 13.0.2, local, l4
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 linux-aarch64 / py3.14, 13.2.0, local, a100
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 linux-aarch64 / py3.11, 13.2.0, local, a100
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 linux-aarch64 / py3.13, 13.0.2, local, a100
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 linux-aarch64 / py3.14t, 12.9.1, local, a100
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 linux-aarch64 / py3.13, 13.2.0, local, a100
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 win-64 / py3.11, 12.9.1, local, v100 (MCDM)
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 win-64 / py3.14t, 12.9.1, local, l4 (TCC)
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 win-64 / py3.13, 12.9.1, local, l4 (TCC)
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 win-64 / py3.14, 13.2.0, local, l4 (MCDM)
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 win-64 / py3.12, 13.0.2, local, a100 (TCC)
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 win-64 / py3.14, 13.0.2, local, l4 (MCDM)
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 win-64 / py3.12, 13.2.0, local, a100 (TCC)
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 win-64 / py3.10, 13.0.2, local, rtxpro6000 (TCC)
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 win-64 / py3.10, 13.2.0, local, rtxpro6000 (TCC)
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/
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
cuda-bindings-python310-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.96 MB |
sha256:f070ff80e04ba198bd5e8c9669506a23f6ed906b9e871fd590bc9edfea3df330
|
|
|
cuda-bindings-python310-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
410 KB |
sha256:8b9fd9e9c1d72d70c8cc351417960e2e0fea60c418af44200f70388a01c4266c
|
|
|
cuda-bindings-python310-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.39 MB |
sha256:a35a964d2fc5a8c1420faf668e286209c88798d8460625eb0169be8b8883a989
|
|
|
cuda-bindings-python310-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
398 KB |
sha256:ae7eabb1a2bbd39da1acd81ce391cd2b919e85564c331b1dbd5433935e4d8b2a
|
|
|
cuda-bindings-python310-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.28 MB |
sha256:8ebe4c462584607a5448c38db8c1951ddf04b1262281816a9be7162690780d27
|
|
|
cuda-bindings-python310-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
63.2 KB |
sha256:1f18f4550dff50e35a29201f4b4ba0aba0f91f87f66e511488cb5956a3efcbb6
|
|
|
cuda-bindings-python311-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.95 MB |
sha256:655ab6eefa19ec546378b714527eba25914aff3f1e63214b11b5c19e84c40c02
|
|
|
cuda-bindings-python311-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
432 KB |
sha256:81b0c8f50b193f499399a7682fea42dbf4a166ad3e59ef8cfae93937a18ac6c0
|
|
|
cuda-bindings-python311-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.38 MB |
sha256:502734e64580fe0fc7ceb4ac0fad68458131cedb21d81ba271c2a2e8b298a1d4
|
|
|
cuda-bindings-python311-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
421 KB |
sha256:fe3310fb27368978df26b1088df7b366fedb4253316953a4d990f4a6061c2a88
|
|
|
cuda-bindings-python311-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.31 MB |
sha256:6be6fc6247669ac5a180d80a8ffa616d5c0dcb4d4ba99aab90fd1f453f862d9b
|
|
|
cuda-bindings-python311-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
63.5 KB |
sha256:e776839668c6df6035bdc1f3fb43c81272006b310334cce5af8a9e4d80d28017
|
|
|
cuda-bindings-python312-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.97 MB |
sha256:cfee984d233dbb791845df9f782d46e3881d2e8d1021f5b79ef25e08caca6f4a
|
|
|
cuda-bindings-python312-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
438 KB |
sha256:5489cfee79484e12d73412fc8f623b16a27ba9129b643544aa6cdf92fb3a16ab
|
|
|
cuda-bindings-python312-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.38 MB |
sha256:e428f042fca2a6fb6cc54ba68a62b79e6ee92639ae42be8fce9a7766631b7d39
|
|
|
cuda-bindings-python312-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
422 KB |
sha256:94bbf27c91e8d9a61549202023eace2c0cb840a121bd534c3c83ac406c8e9b40
|
|
|
cuda-bindings-python312-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.49 MB |
sha256:c0cbb0c3fa7a6b934ee992fcb02988f7700d601ae0b7b0a1ba9ed9497aafb5b5
|
|
|
cuda-bindings-python312-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
62.5 KB |
sha256:c77914599486c4d671da811bcc4e99d95fd64a608ca4ca01751ead38c6c9002e
|
|
|
cuda-bindings-python313-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.8 MB |
sha256:885d5739a70f700fcd86b664d51bc1f0dff2fff9fb1304904129aa87345e9160
|
|
|
cuda-bindings-python313-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
448 KB |
sha256:eed07785efeab89480ae3b0271413584fabbe7d76b38dfd0c381778880b718dd
|
|
|
cuda-bindings-python313-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.27 MB |
sha256:502bc24197c08026258e1ea605238c2574f0a21fd1cf1094f7fdfe4eecd7f060
|
|
|
cuda-bindings-python313-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
430 KB |
sha256:184159ca711449eaa19052e5279942c6f66054eef1270bb28b862a2b00efef76
|
|
|
cuda-bindings-python313-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.45 MB |
sha256:b983b76d05b0e8ae2e322791a57d50612a44a942eb1f8300be4ae62442dce7ca
|
|
|
cuda-bindings-python313-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
62.1 KB |
sha256:6736d8b42c9d1c721537ab38dd54800375e64fb4e4152245569919981092060b
|
|
|
cuda-bindings-python314-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.85 MB |
sha256:e2990f0120aafaccd66a8cae5e1586e549852737a720b9cb1c77f989422581fe
|
|
|
cuda-bindings-python314-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
444 KB |
sha256:acb6aaee3784048d6313105fb0653d66ad12aae78c57651730178409cc16fad8
|
|
|
cuda-bindings-python314-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.34 MB |
sha256:aa8a832bffeb7a4a5b8505c27e9d3d571b8785eab341c9f27ec82e5456552320
|
|
|
cuda-bindings-python314-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
429 KB |
sha256:e686deb23c2391285fce0b55610f2f233db747ad6d5b16167bcaab33638eb20b
|
|
|
cuda-bindings-python314-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.55 MB |
sha256:86d29e558b6037dd9ddf1a0e1a5fc3f58125b93c97df01280350270aa8e91769
|
|
|
cuda-bindings-python314-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
62.8 KB |
sha256:8235346a50404b872d49bd28391174bb398255d483a038e9465a52dec058ea04
|
|
|
cuda-bindings-python314t-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.71 MB |
sha256:2c544039fd6b5dabf550f718290974547bb1a4dc13e73d89fad63c70b0d8c632
|
|
|
cuda-bindings-python314t-cuda13.2.0-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
462 KB |
sha256:b3d37da8ff6a0fec87b674a46f16cabd9d734df3e01eddc8ff212c477db182fa
|
|
|
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
5.17 MB |
sha256:5e10e95fe15a0608e2f1714b010b98d15058323f0fcfacc1f95d35b5384e108d
|
|
|
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
463 KB |
sha256:cd1a827bce46dbbbffd14326e4d5ec4d85082aa105dde0a70583f79220275ef5
|
|
|
cuda-bindings-python314t-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
6.28 MB |
sha256:60cecb101c4d92087f54296038b8ee8f522291ff3f3076f764f96cbd94d84010
|
|
|
cuda-bindings-python314t-cuda13.2.0-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
74.8 KB |
sha256:79139cd0353bebf46aaf344ce69622deb0bf914d3f228bcbfcc0b459427e2d3e
|
|
|
cuda-core-python310-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
22.5 MB |
sha256:17d204f28f54e5b450aeba1769485e473015a622d101c8a3adfd3e8151aa64f1
|
|
|
cuda-core-python310-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
113 KB |
sha256:302785e6f086e470aa863794e66561fede7a865c3619e110cbdcc83ffd1c780d
|
|
|
cuda-core-python310-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
22.3 MB |
sha256:cd8df62907e05e3015f18c51cf74bbdbab9368c7beebf2f01dc39de4723f3fa2
|
|
|
cuda-core-python310-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
112 KB |
sha256:35e7e2d229aa5ae25f5f39d6b436b218258a55bdd838f3cbd3e88ffd9b1ee049
|
|
|
cuda-core-python310-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.29 MB |
sha256:0adcba8c4e9b4012fd730b5182e3e0dc10d9598fa48b842a76ee335c7a515843
|
|
|
cuda-core-python310-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
25.8 KB |
sha256:ceac05c4d8bde2a3ae03fd5313fb6021de08f98bacf3475cd2508ff634c96e4b
|
|
|
cuda-core-python311-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.6 MB |
sha256:471b46b58815400c833bdbf14157c2cba35b49387ca8d075ab925a483f2a29ff
|
|
|
cuda-core-python311-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
118 KB |
sha256:530a8ff71c1b40d381fd6098e51a165a61775d346eedf5031eeebad2b1739442
|
|
|
cuda-core-python311-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.4 MB |
sha256:abfa2c67c1f292272d7a5a518807ea417d9b98cc410dc34ee77246115b969adc
|
|
|
cuda-core-python311-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
117 KB |
sha256:ca2d5ad7e62fe53a558c41965f1299bcf1ecde95bb7c135d3a0e8a6356a230a4
|
|
|
cuda-core-python311-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.29 MB |
sha256:57eff5b886da3b4a2d089ae19707cd6355f4f6d231b1a3b362af99380325851d
|
|
|
cuda-core-python311-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
25.9 KB |
sha256:59aa18476cb963aa1673fa2b13c6e8b47c4e32f88a25fb0d91619fa4660ed221
|
|
|
cuda-core-python312-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.8 MB |
sha256:01366af6a6c462b9287172b398f3bb498a26e77e5441bb6bc0f4d817a97dc311
|
|
|
cuda-core-python312-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
124 KB |
sha256:4a0ccb9dba6cdd9b71acee8996a5e3daf317300de4c120b60ea7b8a4440be26c
|
|
|
cuda-core-python312-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.3 MB |
sha256:79260be2f1f190ecfca6d71822ebcca61afe1ec7c77cefb7a411ef05abebf143
|
|
|
cuda-core-python312-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
122 KB |
sha256:ad041dca7b189345cbc842f75a767f5219bbd85b72c43d954656e8ca7196a678
|
|
|
cuda-core-python312-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.24 MB |
sha256:1170465327ab976794f9f7f7062882ad16fa0371e72a1ffcb27f6c0f68dc328f
|
|
|
cuda-core-python312-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
26.3 KB |
sha256:b0e429c8c32aac1a44856f2a7cada64d2913f183bedc2784d262df266427fac8
|
|
|
cuda-core-python313-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.4 MB |
sha256:4be933106a020c8d8526b25cb35f111ab0c8f246142d5fc583e1377b1c974fc4
|
|
|
cuda-core-python313-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
119 KB |
sha256:c07b739c0c7157afa77b608193a26cad0ea197b17f8c846515299b4e70567a73
|
|
|
cuda-core-python313-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
22.9 MB |
sha256:9de509c96fdb1ce1ac98c2f426b2f267251384688bfc461ded392f9afceb63b0
|
|
|
cuda-core-python313-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
117 KB |
sha256:b68431d51f28c47728eb3dc5b3f995b8137557955a79ed929c22ff569b60be8a
|
|
|
cuda-core-python313-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.23 MB |
sha256:7c7872bdbd524669813b90d880e187d92b3dcf2a1b41999979c5aac8e6920820
|
|
|
cuda-core-python313-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
25.7 KB |
sha256:5b4be783f0f2ef49247dacb7e7c011adb36f5c2d5b413784f96780c1f06861d2
|
|
|
cuda-core-python314-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
23.2 MB |
sha256:e1a3f1c3bd85bad8f8a9f948f49cb27ec926524f496017a97bf05d58cd5c7665
|
|
|
cuda-core-python314-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
118 KB |
sha256:c5a399814201be1caf9dacb4d5fdc1203232ffe98fd91f87484c3ed892505355
|
|
|
cuda-core-python314-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
22.9 MB |
sha256:bf408c91d315bc2cefa38be821a65909dd21b2b41da67b89791fae109a46f942
|
|
|
cuda-core-python314-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
117 KB |
sha256:04b6acc87b46eb4b9bb2c7ae34e5bff3ca9767b2bc94256332c65b8e3587a3fb
|
|
|
cuda-core-python314-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.31 MB |
sha256:331c07de7fdb9ada0b644c3bd96f2fc6fdfc2995410bd57cf91b826a463c4ba7
|
|
|
cuda-core-python314-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
25.7 KB |
sha256:35851c76b494412b2cf292b569685db9143de6cc852e53e1096afa0f0d8b44b8
|
|
|
cuda-core-python314t-linux-64-c17cdea0c57a3ca3428790008455d052cd234039
|
24 MB |
sha256:2093da84b23fb3c352204406235794db5be710c904caf869d3cf98d86aaa0047
|
|
|
cuda-core-python314t-linux-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
142 KB |
sha256:185835e52a5c6c4fc9216bb1a15d5b912aa47782a2bdc7f3102eee1cb6fc2ff4
|
|
|
cuda-core-python314t-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039
|
24.3 MB |
sha256:66bb535caa002448c071f2d61f3326142c131c0c190fada487a80887b5d7800f
|
|
|
cuda-core-python314t-linux-aarch64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
142 KB |
sha256:65a90278548981f4c4ba7259162bc72f53d5df49cd1b468a7beb16ef646d88df
|
|
|
cuda-core-python314t-win-64-c17cdea0c57a3ca3428790008455d052cd234039
|
3.87 MB |
sha256:fa4b6125d883e379fcff6f036b3a4cfa193d90997129d8f5e1d853073c978f2f
|
|
|
cuda-core-python314t-win-64-c17cdea0c57a3ca3428790008455d052cd234039-tests
|
29.2 KB |
sha256:d096caedb71d992856ad68d79247691775283eb2b2a5fcd4d00f3d5ce8932aeb
|
|
|
cuda-pathfinder-wheel
|
42.9 KB |
sha256:11b32833c88157bd95104aa19f9d0a32fb2e5b2bd5c0a54c55993a71c4ffd193
|
|
|
cuda-python-wheel
|
7.78 KB |
sha256:55842affff7e3b726a434f5746100ee00a7a075f4ef24e50f6190b4a88f16c41
|
|