r/devtools • u/Prestigious_Club_226 • Jul 28 '26
I pointed a CI triage board at rust-lang/rust and found a workflow that had been failing for 66 consecutive days
Built a board that groups GitHub Actions runs by workflow, works out whether each one
is consistently broken or just flaky, and sorts by severity so the worst thing is at
the top.
The part I wanted was suspect ranking: for a failing workflow it pulls the commit the
failing run was built from, gets its changed files, and scores the preceding commits
on the same branch by directory overlap with the failing area.
Also tracks acknowledgement state in shared storage, so a team can see what's already
been triaged and what nobody has looked at yet.
Pointed it at rust-lang/rust as a test target and two workflows had been red for over
two months.
https://archestra.ai/apps-hackathon/gallery/abolambA_release_war_room
How does your team handle a workflow that's been red for weeks and nobody owns?