Skip to content

nightly

nightly #24

Triggered via schedule June 23, 2024 00:24
Status Failure
Total duration 25m 46s
Billable time 2m
Artifacts

nightly.yml

on: schedule
unused-dependencies
1m 13s
unused-dependencies
Prove integration tests and examples
4m 55s
Prove integration tests and examples
Matrix: linux-exhaustive
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Prove integration tests and examples
Process completed with exit code 2.
Exhaustive tests on x86
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Exhaustive tests on x86
The operation was canceled.
Exhaustive tests on ARM
The self-hosted runner: warp-32x-arm64-w8xuwbq6p2ch140n 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.