Closed Bug 1519136 Opened 3 years ago Closed 2 months ago

Intermittents case study: Why is bug 1490978 not resolved?

Categories

(Testing :: General, defect, P3)

Version 3
defect

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

According to treeherder's intermittent failures view, bug 1490978 has failed about 402 times between Oct 1 2018 and January 10, 2019. The failure rate seems approximately constant over that period (25-35 failures per week). The IF bot has changed the whiteboard status several times back and forth between [stockwell needswork:owner] and [stockwell unknown] (current status).

Why is this bug not being resolved?

Should the IF bot have marked it disabled-recommended?

Why did the IF bot set [stockwell unknown] a couple of times?

Why is the triage owner not responding?

Why did several attempts to find a regression range fail? (And did those delay or confuse efforts to resolve the failures?)

Let's use this as a case study to see if the IF bot rules can be improved and whether policy changes would improve outcomes.

Priority: -- → P3

Bug 1424166 seems like a similar case.

Assignee: nobody → whole.grains
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.