Repository navigation
[nightly-verify] main is red #1018
Description
The nightly make verify run on self-hosted-macos-26-arm64 failed. At least one of the three gates below is genuinely red on the commit named at the bottom.
| Field | Value |
|---|---|
verify job result |
failure |
make verify-fmt |
failure |
make verify-clippy |
failure |
make verify-test |
failure |
| Trigger | workflow_dispatch |
Duration of the verify job: 0m16s.
Commit: 0aa182486c0e7432006ec1fe59a781510954766d
Run: https://github.com/lablup/mlxcel/actions/runs/30870790330
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.
Activity
inureyes commentedon Aug 4, 2026
Closing: this was filed by the new reporting job during its own end-to-end verification, not by a genuine code regression.
Run 30870790330 died in
Ensure build toolsbecause Homebrew was not on the runner's PATH, 16 seconds in, before any gate could run. The three gates then reportedfailureonly because the toolchain step had been skipped, which is why this issue's body reads as though the code is red. Both the runner defect and that misleading headline are fixed in #1017 (a6cf4b5bb).Verified afterwards on run 30871982545:
verifysucceeded and the report job correctly stayedskipped.