[nightly-verify] main is red #1256

Activity

1. github-actions

   added

   status:readyReady to be worked onReady to be worked on

   type:bugBug fixes, error corrections, or issue resolutionsBug fixes, error corrections, or issue resolutions

   priority:highHigh priorityHigh priority

   on Aug 19, 2026
2. github-actions commented on Aug 21, 2026

   

   github-actionsBot

   on Aug 21, 2026 – with GitHub Actions

   Author

   More actions

   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	failure
   make verify-test	success
   make verify-test-video	success
   Trigger	schedule

   Duration of the verify job: 53m41s.

   Commit: dd21ada47260ea2d8c9b53689a27bcab3c285240
   Run: https://github.com/lablup/mlxcel/actions/runs/32511932812

   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.
3. github-actions commented on Aug 23, 2026

   

   github-actionsBot

   on Aug 23, 2026 – with GitHub Actions

   Author

   More actions

   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: 32m23s.

   Commit: 6ecf756ecf81f4c039617ab9927ec4b862ee7919
   Run: https://github.com/lablup/mlxcel/actions/runs/32656970039

   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.
4. github-actions commented on Aug 24, 2026

   

   github-actionsBot

   on Aug 24, 2026 – with GitHub Actions

   Author

   More actions

   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: 25m10s.

   Commit: fa4bd5c6fa36d8b8f1d63f1ecaa16118e0985c50
   Run: https://github.com/lablup/mlxcel/actions/runs/32760920343

   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.
5. github-actions commented on Aug 25, 2026

   

   github-actionsBot

   on Aug 25, 2026 – with GitHub Actions

   Author

   More actions

   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: 12m53s.

   Commit: 681d3656b88f6702b975451a0deab9df8a37b30a
   Run: https://github.com/lablup/mlxcel/actions/runs/32882245154

   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.
6. github-actions commented on Aug 27, 2026

   

   github-actionsBot

   on Aug 27, 2026 – with GitHub Actions

   Author

   More actions

   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: 9m21s.

   Commit: e897a35579408e387b120a9ef995ec75bfbd6be2
   Run: https://github.com/lablup/mlxcel/actions/runs/33117206403

   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.
7. github-actions commented on Aug 29, 2026

   

   github-actionsBot

   on Aug 29, 2026 – with GitHub Actions

   Author

   More actions

   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: 9m39s.

   Commit: b2be0d0ab36b17ba35e9ae9d96fe7f19a195d5df
   Run: https://github.com/lablup/mlxcel/actions/runs/33267726750

   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.
8. github-actions commented on Aug 30, 2026

   

   github-actionsBot

   on Aug 30, 2026 – with GitHub Actions

   Author

   More actions

   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: 15m58s.

   Commit: 365408ace05c52bbfc91de48541de9bc2628d0b3
   Run: https://github.com/lablup/mlxcel/actions/runs/33327488319

   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.
9. github-actions commented on Aug 31, 2026

   

   github-actionsBot

   on Aug 31, 2026 – with GitHub Actions

   Author

   More actions

   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: 17m45s.

   Commit: 8b4a25cb7007c780ab8a8d5df425ca097d27de38
   Run: https://github.com/lablup/mlxcel/actions/runs/33424171221

   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.
10. inureyes

    added

    status:in-progressCurrently being worked onCurrently being worked on

    and removed

    status:readyReady to be worked onReady to be worked on

    on Sep 1, 2026
11. inureyes

    added a commit that references this issue on Sep 1, 2026

    fix: tighten verify-test snapshot bounds

    ...

    b18ad1b
12. inureyes

    added

    status:doneCompletedCompleted

    and removed

    status:in-progressCurrently being worked onCurrently being worked on

    on Sep 1, 2026
13. inureyes

    closed this as completedin #1567on Sep 1, 2026
14. be-free-snowboy

    added a commit that references this issue on Sep 3, 2026

    fix: stabilize nightly verify-test failures (lablup#1256) (lablup#1567)

    ...

    e278d01