Skip to content
Nightly Testing

Nightly Testing #30

Sign in to view logs

Nightly Testing

Nightly Testing #30

Triggered via schedule December 11, 2024 00:31
@github-merge-queuegithub-merge-queue[bot]
⁠ d0a06c5
master
Status Failure
Total duration 3h 46m 49s
Artifacts –

nightly.yml

on: schedule
Linux placeholder testing and sanitize with clang  /  Build and test Linux with clang
2h 51m
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Post test results in Open Telemetry format
52m 57s
Post test results in Open Telemetry format
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Exception: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang: results/keccak_test.xml#L1
Error processing result file: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Exception: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang: results/blueprint_plonk_non_native_field_test.xml#L1
Error processing result file: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Exception: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang: results/blueprint_zkevm_rw_test.xml#L1
Error processing result file: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang
Exception: File is empty.
Linux placeholder testing and sanitize with clang / Build and test Linux with clang: results/sha3_test.xml#L1
Error processing result file: File is empty.
Post test results in Open Telemetry format
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Post test results in Open Telemetry format
The self-hosted runner: nil-githhub-actions_i-07a852f7a8fda233c 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.