CI: skip ut-a5 while the a5 runner is under repair - #1533
Conversation
The a5 self-hosted runner is out for repair, so ut-a5 has no host to run on and sits waiting for one instead of reporting a result. Short- circuiting its existing gate with `false &&` makes it report skipped, mirroring what hw-native-sys#1481 already did for st-onboard-a5 on the same runner. Nothing declares `needs: ut-a5` and main has no required status checks, so the job's absence blocks no merge. Coverage for a5 changes falls back to st-sim-a5, which runs on GitHub-hosted runners.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe GitHub Actions ChangesCI job gating
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The a5 self-hosted runner is out for repair, so
ut-a5has no host to run on and sits waiting for one instead of reporting a result. This short-circuits its existing gate withfalse &&so it reports skipped, mirroring exactly what #1481 already did forst-onboard-a5on the same runner.Nothing declares
needs: ut-a5andmainhas no required status checks, so the job's absence blocks no merge. Coverage for a5 changes falls back tost-sim-a5, which runs on GitHub-hosted runners.To re-enable once the runner returns: drop the
false &&from theif:gate (same as the note left onst-onboard-a5).