Skip to content

Nightly-OnDemand Tests Rolling #31

Nightly-OnDemand Tests Rolling

Nightly-OnDemand Tests Rolling #31

Triggered via schedule August 30, 2024 16:34
Status Failure
Total duration 1d 23h 23m 32s
Artifacts
Linux-Nightly-Ondemand-E2E-Tests-Rolling
6h 49m
Linux-Nightly-Ondemand-E2E-Tests-Rolling
Linux-Nightly-Ondemand-UT-Tests-Rolling  /  Torch-XPU-UT-Tests
0s
Linux-Nightly-Ondemand-UT-Tests-Rolling / Torch-XPU-UT-Tests
Linux-Weekly-UT-Tests-ABI-0-Rolling  /  Torch-XPU-UT-Tests
0s
Linux-Weekly-UT-Tests-ABI-0-Rolling / Torch-XPU-UT-Tests
Tests-Failure-And-Report
3s
Tests-Failure-And-Report
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Linux-Nightly-Ondemand-E2E-Tests-Rolling
The self-hosted runner: pytorch-08 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.
Linux-Weekly-UT-Tests-ABI-0-Rolling / Torch-XPU-UT-Tests
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Linux-Nightly-Ondemand-UT-Tests-Rolling / Torch-XPU-UT-Tests
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.