Skip to content
Nightly Binaries Validations

Nightly Binaries Validations #330

Sign in to view logs

Nightly Binaries Validations

Nightly Binaries Validations #330

Triggered via schedule August 1, 2025 15:36
@atalmanatalman
⁠ 53cff80
main
Status Failure
Total duration 3h 6m 49s
Artifacts –

validate-nightly-binaries.yml

on: schedule
nightly  /  ...  /  generate
4s
nightly / generate-release-matrix / generate
nightly  /  ...  /  generate
7s
nightly / linux-aarch64 / generate-aarch64-linux-matrix / generate
nightly  /  ...  /  generate
6s
nightly / linux / generate-linux-matrix / generate
nightly  /  ...  /  generate
6s
nightly / mac-arm64 / generate-macos-arm64-matrix / generate
nightly  /  ...  /  generate
5s
nightly / win / generate-windows-matrix / generate
nightly  /  ...  /  amazon-linux-2023-test
5m 16s
nightly / linux / amazon-linux-2023-test / amazon-linux-2023-test
Matrix: nightly / linux-aarch64 / linux-aarch64
Matrix: nightly / linux / linux
Matrix: nightly / mac-arm64 / macos-arm64
Matrix: nightly / win / win
Fit to window
Zoom out
Zoom in

Annotations

1 error
nightly / win / wheel-py3_13-cuda12_6 / wheel-py3_13-cuda12_6
The self-hosted runner 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.