Skip to content
Run Bazel GPU tests locally

[test] try to find out why GPUs are not being utilized correctly #113

Sign in to view logs

[test] try to find out why GPUs are not being utilized correctly

[test] try to find out why GPUs are not being utilized correctly #113

Triggered via pull request September 27, 2024 13:37
@MichaelHudginsMichaelHudgins
opened #27
michael/test-jax-gpu
Status Failure
Total duration 8m 0s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

bazel_gpu_local.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
build (linux-x86-g2-48-l4-4gpu-driver-555)
Error: failed to run script step: command terminated with non-zero exit code: error executing command [sh -e /__w/_temp/af2c5b20-7cd6-11ef-9229-dfa4795fc9a6.sh], exit code 127
build (linux-x86-g2-48-l4-4gpu-driver-555)
Process completed with exit code 1.
build (linux-x86-g2-48-l4-4gpu-driver-555)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
build (linux-x86-g2-48-l4-4gpu-driver-555)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/