Skip to content

Nightly Testing

Nightly Testing #95

Triggered via schedule February 14, 2025 00:28
Status Failure
Total duration 3h 33m 12s
Artifacts

nightly.yml

on: schedule
Linux placeholder testing and sanitize with clang  /  Build and test Linux with clang
2h 15m
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Gcc debug proof-producer Linux testing  /  Build proof-producer binary in debug mode
3h 30m
Gcc debug proof-producer Linux testing / Build proof-producer binary in debug mode
Build deb package  /  Build proof-producer deb package
28s
Build deb package / Build proof-producer deb package
Post test results in Open Telemetry format
0s
Post test results in Open Telemetry format
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Process completed with exit code 137.
Post test results in Open Telemetry format
The self-hosted runner: nil-githhub-actions_i-06159437481924f3e 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.