Skip to content

Nightly

Nightly #52

Triggered via schedule July 28, 2026 06:55
Status Success
Total duration 51m 32s
Artifacts 2

nightly.yml

on: schedule
Build Linux nightly assets
6m 31s
Build Linux nightly assets
E2E tests (GPU, incl. nightly-only)
12m 28s
E2E tests (GPU, incl. nightly-only)
E2E tests (Strix Halo, incl. nightly-only)
17m 20s
E2E tests (Strix Halo, incl. nightly-only)
E2E tests (Strix Halo, Windows, incl. nightly-only)
51m 4s
E2E tests (Strix Halo, Windows, incl. nightly-only)
Build and upload Windows nightly
12m 51s
Build and upload Windows nightly
Publish nightly
1m 36s
Publish nightly
Clean failed nightly staging release
0s
Clean failed nightly staging release
Fit to window
Zoom out
Zoom in

Annotations

1 error
E2E tests (Strix Halo, Windows, incl. nightly-only)
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.

Artifacts

Produced during runtime
Name Size Digest
e2e-gpu-nightly-report
31.9 KB
sha256:71cac19b1a5b52cb4d6d93882f93aae6635f02ba83a7710193220c8541ce9d03
e2e-gpu-nightly-strix-report
33 KB
sha256:bd290edd40c8cd2bc5cdf3bc849aeca5a224c33d0596b006abb0c400d081bf61