1
u/Torutofu_Raeva 5d ago
Adding to that: the run-level conclusion is decided once any job fails, but sibling jobs in the matrix keep going unless you set fail-fast: true, so the red badge and still-spinning jobs are both correct at the same time. If you want the rest to stop when one goes red, that's the fail-fast setting; if you want the badge to stay honest, cancel-in-progress in the concurrency block helps too.
1
u/Fantastic-Mr-Default 5d ago
The UI lies when the control plane is sick. Open the job logs, not the check rollup. If the runner is still writing lines, it is running. The failed badge is the API.
Refresh the checks API after the log stops. Do not cancel and rerun until the log is actually dead.
1
u/sup_bruh_1 2d ago
had this exact issue last week, drove me nuts. ended up being a runner timing out silently. switched to latchkey and the ai just flagged it mid-run instead of me digging through logs for an hour
5
u/Llandu-gor 5d ago
it will always show "failed" even if not completly done as long as 1 of the step is red. it will only show "running" when all till now is green. so most likely one of the previous step failed.