Open Bug 1421365 Opened 7 years ago Updated 2 years ago

Allow "unclassified" mode to show duplicate jobs of failures, regardless of result

Categories

(Tree Management :: Treeherder: Frontend, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: aryx, Unassigned)

References

Details

• If a new failure is discovered, sheriffs shall check if it’s a permanent failure and if possible also if it’s a frequent failure. For that reason, they will retrigger the job. By default, the sheriffs don’t have the display of pending, running and successful jobs enabled because they increase the height of each push very much, and for that reason they will have to open a new Treeherder tab with either that push and the job selected or filtered by the job signature to keep a usable view for the main Treeherder tab and revisit the retriggers when they are done. • All jobs with an identic configuration should be shown if at least one of them failed (with “failed” meaning “busted” or “testfailed” - not “exception”).
This would be similar logic to the "Duplicates" button that's used to exclude jobs from grouping. We could detect on a given push if there's a failed test and any test with the same signature, regardless of result would be displayed. Not sure if this should be the default for sheriffs or something that could be toggled on. So this would be handled in the UI rendering code, rather than in jobfilters.js. jobfiltesr.js only looks at one job at a time, whereas the rendering code can look at several jobs at a time.
Summary: New view: Show only failures and successful, running and pending jobs for identic job → Allow "unclassified" mode to show duplicate jobs of failures, regardless of result
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.