Skip to content

Docker Images CI

Docker Images CI #351

Triggered via schedule October 10, 2023 02:11
Status Failure
Total duration 2h 10m 7s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

main.yml

on: schedule
build-r1OpenPose
4m 22s
build-r1OpenPose
Matrix: build-tour-docker-sim
Matrix: build-tour-docker
Fit to window
Zoom out
Zoom in

Annotations

8 errors
build-r1OpenPose
Process completed with exit code 1.
build-tour-docker-sim (iron, nvidia/cuda:11.7.1-cudnn8-devel-ubuntu22.04, cuda.11.7.1-cudnn8)
The hosted runner: GitHub Actions 7 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-tour-docker-sim (iron, ubuntu:22.04, ubuntu22.04)
The hosted runner: GitHub Actions 8 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-tour-docker (iron, ubuntu:22.04, ubuntu22.04)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
build-tour-docker (iron, ubuntu:22.04, ubuntu22.04)
The hosted runner: GitHub Actions 5 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-tour-docker (iron, ubuntu:22.04, ubuntu22.04)
Process completed with exit code 143.
build-tour-docker (iron, nvidia/cuda:11.7.1-cudnn8-devel-ubuntu22.04, cuda.11.7.1-cudnn8)
The job was canceled because "iron_ubuntu_22_04_ubuntu2" failed.
build-tour-docker (iron, nvidia/cuda:11.7.1-cudnn8-devel-ubuntu22.04, cuda.11.7.1-cudnn8)
The hosted runner: GitHub Actions 6 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.