Skip to content
multiprocess-tests-schedule-run

multiprocess-tests-schedule-run #52

Sign in to view logs

multiprocess-tests-schedule-run

multiprocess-tests-schedule-run #52

Triggered via schedule November 20, 2025 00:25
@copybara-servicecopybara-service[bot]
⁠ d966ddf
main
Status Failure
Total duration 13m 22s
Artifacts –

multiprocess_tests.yml

on: schedule
Matrix: multiprocess-checkpoint-benchmarks
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 6 warnings, and 15 notices
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Process completed with exit code 1.
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Error: Job failed with exit code 1.
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
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
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
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
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
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
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
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
multiprocess-checkpoint-benchmarks (Python 3.12, jax=0.6.0)
The strategy configuration was canceled because "multiprocess-checkpoint-benchmarks._3_11_0_6_0" failed
multiprocess-checkpoint-benchmarks (Python 3.10, jax=0.6.0)
The strategy configuration was canceled because "multiprocess-checkpoint-benchmarks._3_11_0_6_0" failed
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 error
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 3 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 2 output
multiprocess-checkpoint-benchmarks (Python 3.11, jax=0.6.0)
Job 1 output