Skip to content

ci: use self-hosted to build container images (#1206) #3066

ci: use self-hosted to build container images (#1206)

ci: use self-hosted to build container images (#1206) #3066

Re-run triggered October 27, 2023 12:57
Status Failure
Total duration 3h 25m 7s
Artifacts

image.yml

on: push
Matrix: docker
Fit to window
Zoom out
Zoom in

Annotations

7 errors
docker (cublas, 11, 7, linux/amd64, false, -cublas-cuda11)
The self-hosted runner: docker-runner-github-runner-574ff67d75-wv8r9 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.
docker (cublas, 11, 7, linux/amd64, false, -cublas-cuda11-ffmpeg, true)
The job was canceled because "cublas_11_7_linux_amd64_f" failed.
docker (cublas, 11, 7, linux/amd64, false, -cublas-cuda11-ffmpeg, true)
The self-hosted runner: docker-runner-github-runner-574ff67d75-sdp2k 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.
docker (cublas, 12, 1, linux/amd64, false, -cublas-cuda12-ffmpeg, true)
The job was canceled because "cublas_11_7_linux_amd64_f" failed.
docker (cublas, 12, 1, linux/amd64, false, -cublas-cuda12-ffmpeg, true)
The self-hosted runner: docker-runner-github-runner-574ff67d75-jwbgg 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.
docker (cublas, 12, 1, linux/amd64, false, -cublas-cuda12)
The job was canceled because "cublas_11_7_linux_amd64_f" failed.
docker (cublas, 12, 1, linux/amd64, false, -cublas-cuda12)
The self-hosted runner: docker-runner-github-runner-574ff67d75-pxw4b 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.