Closed Bug 825654 Opened 13 years ago Closed 10 years ago

TBPL should bubble RETRIES up to onlyunstarred=1 when they repeat enough.

Categories

(Tree Management Graveyard :: TBPL, defect)

Product:
Tree Management Graveyard
Component:
TBPL
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Callek, Unassigned)

Details

(Keywords: sheriffing-P2)

So today, I did a tools deploy for android jobs, and it caused a large string of retries due to a code error in cleanup.py (as run from verify.py) Philor would have normally caught it and screamed at me earlier, if not for the fact that retries are hidden on onlyunstarred=1 I suggest we show *all* retries (of a job) in that view when we get 3 or more retries for a specific job on a specific revision. Is this too hard? Thoughts?
I seem to have thought it would be a good idea in bug 697994 comment 1.
These type of failures (and also things like many failures on one particular slave) are something I'd definitely like us to be able to handle better in TBPlv2.
Keywords: sheriffing-P2
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
Filed bug 1164179 for treeherder.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.