Open Bug 1746673 Opened 2 years ago

Color-code oranges by how good of a match existing bugs are to them

Categories

(Tree Management :: Treeherder: Frontend, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: jgilbert, Unassigned)

Details

For example:
https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=C1WaCS8fSAeLz-qEvYd2uQ.0&revision=43d9dbe7c7d166c66e63720ecc3d65604edeb8fa

Right now, I have no idea looking at this whether this is "clean". I have to go through 40ish different failing tasks, the vast majority of which have exact text matches to existing known intermittants.
We should color-code these accordingly.

Otherwise, and I'm not proud to admit it, I tend towards just pushing straight to Lando, because Try runs with oranges are not great signals of whether a push is ready. In my experience I'll frequently try to push to Try, evaluate the run as "likely clean", and push to Lando just to be backed out. In this case, I've more than doubled the machine-time cost by pushing twice, and both me and a sheriff have had to spend time evaluating pushes.
Realistically, I expect that others end up making the same gamble, costing us human and machine time in the process.

So let's automate this a little bit!
Maybe good-match oranges can be yellow instead?

You need to log in before you can comment on or make changes to this bug.