Skip to content

Add system-benchmarks container #110

Add system-benchmarks container

Add system-benchmarks container #110

Triggered via push December 3, 2024 12:59
Status Failure
Total duration 1h 20m 38s
Artifacts

spacktainer.yaml

on: push
builder-container-job
5m 1s
builder-container-job
runtime-container-job
52s
runtime-container-job
Matrix: spacktainer-build-job
Fit to window
Zoom out
Zoom in

Annotations

4 errors
spacktainer-build-job (functionalizer)
The self-hosted runner: 76168bf4-234f-4c07-bd94-bf953fb6d071 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.
spacktainer-build-job (brayns)
The self-hosted runner: d1b1018f-2b1a-4a5f-9a89-f6a930312916 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.
spacktainer-build-job (connectome-manipulator)
The self-hosted runner: 58282019-8324-4e26-b84e-9faa2113c0db 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.
spacktainer-build-job (multiscale-run)
The self-hosted runner: 8068b5df-1751-4ebe-b188-69501bb50795 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.