The nightly make verify run on self-hosted-macos-26-arm64 failed. Check the first failing step in the run log before reading the gate table below: a setup step that fails leaves the gates reporting failure for want of a toolchain rather than because the code is red.
| Field |
Value |
verify job result |
failure |
make verify-fmt |
success |
make verify-clippy |
success |
make verify-test |
failure |
make verify-test-video |
success |
| Trigger |
schedule |
Duration of the verify job: 52m49s.
Commit: 9e2c667532784143639fd15666df7f03d14a881a
Run: https://github.com/lablup/mlxcel/actions/runs/32285735051
An unknown step outcome means the job published no outcome for that step. A timeout-minutes cancellation still publishes them, so unknown points at the runner being lost outright rather than at the budget.
Reproduce locally with make verify (or the single failing target above).
This issue is reused by subsequent nightly reports of the same kind while it stays open.
The nightly
make verifyrun onself-hosted-macos-26-arm64failed. Check the first failing step in the run log before reading the gate table below: a setup step that fails leaves the gates reportingfailurefor want of a toolchain rather than because the code is red.verifyjob resultfailuremake verify-fmtsuccessmake verify-clippysuccessmake verify-testfailuremake verify-test-videosuccessscheduleDuration of the
verifyjob: 52m49s.Commit:
9e2c667532784143639fd15666df7f03d14a881aRun: https://github.com/lablup/mlxcel/actions/runs/32285735051
An
unknownstep outcome means the job published no outcome for that step. Atimeout-minutescancellation still publishes them, sounknownpoints at the runner being lost outright rather than at the budget.Reproduce locally with
make verify(or the single failing target above).This issue is reused by subsequent nightly reports of the same kind while it stays open.