Skip to content

Oops, cannot have error sync here. #455

Oops, cannot have error sync here.

Oops, cannot have error sync here. #455

Triggered via push August 15, 2023 13:27
Status Failure
Total duration 1h 25m 52s
Artifacts 2
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

benchmark.yml

on: push
benchmark-MI100-opencl
32m 38s
benchmark-MI100-opencl
benchmark-A100
0s
benchmark-A100
benchmark-titanx-cuda
0s
benchmark-titanx-cuda
benchmark-titanx-opencl
0s
benchmark-titanx-opencl
benchmark-titanrtx-cuda
0s
benchmark-titanrtx-cuda
benchmark-titanrtx-opencl
0s
benchmark-titanrtx-opencl
benchmark-results
0s
benchmark-results
Fit to window
Zoom out
Zoom in

Annotations

5 errors
benchmark-titanrtx-cuda
The self-hosted runner: hendrix3 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.
benchmark-titanx-cuda
The self-hosted runner: hendrix0 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.
benchmark-titanx-opencl
The self-hosted runner: hendrix1 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.
benchmark-A100
The self-hosted runner: hendrix2 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.
benchmark-titanrtx-opencl
The self-hosted runner: hendrix4 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.

Artifacts

Produced during runtime
Name Size
futhark-nightly-linux-x86_64.tar.xz Expired
6.01 MB
futhark-opencl-MI100-a7adb905d828e76747d730756755a95b3e590805.json Expired
2.28 MB