[nightly-verify] main is red #1599

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

   

   github-actionsBot

   on Sep 3, 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: 16m4s.

   Commit: b2ff1eee96e6f30bdd3a5abb415498dde2f1067d
   Run: https://github.com/lablup/mlxcel/actions/runs/33789607902

   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 Sep 4, 2026

   

   github-actionsBot

   on Sep 4, 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: 14m48s.

   Commit: 64e8d9a8b991e750fe58faff2b0e15cc377017fd
   Run: https://github.com/lablup/mlxcel/actions/runs/33904935685

   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 Sep 5, 2026

   

   github-actionsBot

   on Sep 5, 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: 16m3s.

   Commit: 9bef3f2334c4048d8540aa392ef030c97d4dad2c
   Run: https://github.com/lablup/mlxcel/actions/runs/33983424065

   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 Sep 6, 2026

   

   github-actionsBot

   on Sep 6, 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: 9m1s.

   Commit: bb8dd8240489c6c2702ac8c9870e78a3dafc5809
   Run: https://github.com/lablup/mlxcel/actions/runs/34051078957

   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 Sep 7, 2026

   

   github-actionsBot

   on Sep 7, 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: 9m6s.

   Commit: bb8dd8240489c6c2702ac8c9870e78a3dafc5809
   Run: https://github.com/lablup/mlxcel/actions/runs/34150956559

   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 Sep 8, 2026

   

   github-actionsBot

   on Sep 8, 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: 9m17s.

   Commit: 0accedd90ae9ea0679121bd087dafdd82882182a
   Run: https://github.com/lablup/mlxcel/actions/runs/34262127778

   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 Sep 10, 2026

   

   github-actionsBot

   on Sep 10, 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: 16m15s.

   Commit: 86d35b2f25fde87172f429eb485206dfc23a0513
   Run: https://github.com/lablup/mlxcel/actions/runs/34513246160

   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 Sep 28, 2026

   

   github-actionsBot

   on Sep 28, 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: 10m17s.

   Commit: 26b53f0246c3910e073f24310660569f1fbcc1c6
   Run: https://github.com/lablup/mlxcel/actions/runs/36464262071

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

    

    github-actionsBot

    on Sep 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: 18m23s.

    Commit: d913fc7d737db98004c70c038c97b9454d4b3da7
    Run: https://github.com/lablup/mlxcel/actions/runs/36611112322

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

    

    github-actionsBot

    on Sep 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: 17m52s.

    Commit: 78af3e2df9c8186be3f5ba71cb68c24527a2c1bd
    Run: https://github.com/lablup/mlxcel/actions/runs/36757563932

    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.
12. github-actions commented on Oct 1, 2026

    

    github-actionsBot

    on Oct 1, 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: 2m5s.

    Commit: 78af3e2df9c8186be3f5ba71cb68c24527a2c1bd
    Run: https://github.com/lablup/mlxcel/actions/runs/36905958058

    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.
13. github-actions commented on Oct 2, 2026

    

    github-actionsBot

    on Oct 2, 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: 10m55s.

    Commit: c0b71344c032177d495637422c7af50949d97fea
    Run: https://github.com/lablup/mlxcel/actions/runs/37046630998

    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.
14. 18 remaining items

    Load more
15. inureyes

    added 5 commits that reference this issue on Oct 13, 2026

    chore: merge main into Metal gather fix

    ...

    1a3d0ef

    fix(metal): make the nightly candidate portable

    ...

    b6b45b5

    chore: merge latest main into Metal nightly fix

    ...

    5157f96

    docs: record the final main sync for PR #2138

    ...

    2dbffe6

    docs: record verified Metal candidate results

    ...

    eecb628
16. github-actions commented on Oct 13, 2026

    

    github-actionsBot

    on Oct 13, 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: 32m52s.

    Commit: 4b0c451955e3089e3931e0e3fbcf6bd0e7b561e0
    Run: https://github.com/lablup/mlxcel/actions/runs/38445842641

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

    added 2 commits that reference this issue on Oct 14, 2026

    chore: merge current main into Metal nightly fix

    ...

    4404552

    docs: complete Metal nightly fix attribution

    ...

    bb687a9
18. inureyes

    closed this as completedin #2304on Oct 14, 2026
19. inureyes

    added 3 commits that reference this issue on Oct 14, 2026

    update: advance MLX pin and reconcile backend ownership (#2304)

    ...

    9bfabba

    fix: reconcile Metal nightly fix with the new MLX pin

    ...

    d04b073

    update: reconcile Metal nightly fix with current MLX pin (#2138)

    ...

    adf0e58
20. inureyes commented on Oct 14, 2026

    

    inureyes

    on Oct 14, 2026

    Member

    More actions

    Post-merge main Metal verification is now complete: run 38593621616 passed on adf0e589, after #2304 and #2138. Formatting and Clippy passed; the general suite passed 12,317 tests with 390 ignored, and the FFmpeg video gate passed 51 tests. There were no failures. The subsequent main commit c0ae26b2 adds only the #2313 security-validation reports.

    This supplies the required post-merge Metal nightly evidence for #1599, beyond the earlier candidate runs. M5-specific execution remains unverified and #2158 remains deferred; #1986 continues separately.
21. inureyes

    added

    status:doneCompletedCompleted

    and removed

    status:reviewUnder reviewUnder review

    on Oct 14, 2026