[HUD] Show unstable-marked jobs on the reliability page - #8419
Open
georgehong wants to merge 2 commits into
Open
[HUD] Show unstable-marked jobs on the reliability page#8419georgehong wants to merge 2 commits into
georgehong wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
The 'Unstable jobs' panel only matched the dedicated 'unstable' workflow (green scaffolding), so jobs marked unstable via 'UNSTABLE ...' issues -- which keep running on main with an ', unstable' config marker -- were never shown. Add an unstableOnly toggle to master_commit_red_jobs: 0 keeps the existing workflow-scoped behavior (verified byte-identical); 1 flips the filter to show the union of the dedicated 'unstable' workflow and any job marked unstable on main (workflow_run- chained jobs excluded, as in normal mode). Point the panel at it with unstableOnly=1. Reuses the shared query instead of a fork.
georgehong
force-pushed
the
reliability-unstable-jobs-panel
branch
from
August 3, 2026 20:51
69180c9 to
584732c
Compare
Contributor
Author
|
Reliability page available at: https://torchci-git-reliability-unstable-jobs-panel-fbopensource.vercel.app/reliability |
Name the two groups the panel unions and say the marker is applied at runtime, so the subtitle doesn't read as the filed UNSTABLE issue list.
Contributor
Author
|
Note: there's a moderate drain effect where non-unstable history may show the same job being present in both the stable and unstable panel(s). I think it's useful to surface cordoned jobs so they may have recovery monitored in the span of a few days to week(s), but this may be subject to discussion to ensure there's no user confusion. The alternative may require some form of matching between unstable jobs, issue open/close timing history, and revising the job history, and we would need to update the existing panels. |
georgehong
marked this pull request as ready for review
August 3, 2026 23:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, Unstable jobs panel feels a bit narrow since it was only including jobs part of the unstable workflow. Expand the query to also include jobs marked as unstable (e.g. with the Issue workflow). This provides a flow for users to monitor cordoned jobs and improvements in reliability.