Test CI scripts and workflows #221
Triggered via pull request
November 20, 2024 17:41
nitins17
Status
Failure
Total duration
30m 41s
Artifacts
–
pytest_cpu.yml
on: pull_request
Build the jaxlib aritfact using latest XLA
/
determine_matrix
7s
Matrix: Build the jaxlib aritfact using latest XLA / build_artifacts
Matrix: Run CPU tests with Pytest
Annotations
23 errors
|
Build the jaxlib aritfact using latest XLA / build_artifacts (windows-x86-n2-64, jaxlib, 3.11)
Process completed with exit code 1.
|
|
Build the jaxlib aritfact using latest XLA / build_artifacts (windows-x86-n2-64, jaxlib, 3.13)
Process completed with exit code 1.
|
|
Build the jaxlib aritfact using latest XLA / build_artifacts (windows-x86-n2-64, jaxlib, 3.12)
Process completed with exit code 1.
|
|
Build the jaxlib aritfact using latest XLA / build_artifacts (windows-x86-n2-64, jaxlib, 3.10)
Process completed with exit code 1.
|
|
Run CPU tests with Pytest (windows-x86-n2-64, 3.10)
Process completed with exit code 1.
|
|
Run CPU tests with Pytest (windows-x86-n2-64, 3.11)
Process completed with exit code 1.
|
|
Run CPU tests with Pytest (windows-x86-n2-64, 3.12)
Process completed with exit code 1.
|
|
Run CPU tests with Pytest (windows-x86-n2-64, 3.13)
Process completed with exit code 1.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.10)
The self-hosted runner: linux-x86-n2-64-crd2l-runner-mcnhr lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.10)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.10)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.11)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.11)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.12)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.12)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.13)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.13)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.11)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.11)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.13)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-arm64-t2a-48, 3.13)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.12)
The job was canceled because "linux-x86-n2-64_3_10" failed.
|
|
Run CPU tests with Pytest (linux-x86-n2-64, 3.12)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|