Don't group successful jobs that match a failed job.
Categories
(Tree Management :: Treeherder: Frontend, enhancement)
Tracking
(Not tracked)
People
(Reporter: bobowen, Unassigned)
Details
On a large try push with the inevitable intermittent failures, I will often retrigger each one before matching it to a bug.
If and when the retry succeeds it will get grouped with the other successful ones, which means I have to ungroup to find it and check that I have done a retrigger.
It would be really useful if successful jobs that match a failed job were not grouped.
|
||
Comment 1•6 years ago
|
||
Seconded.
check that I have done a retrigger
Or that it has finished.
Expanding also adds a lot of visual clutter that this would avoid. That, in combination with avoiding all the clicks to expand, would be a nice win in reducing a bit of friction we regularly encounter.
|
||
Comment 2•6 years ago
|
||
There is a button on the toolbar to make these jobs visible. The "duplicates" button will prevent any job that has more than one occurrence in the platform from getting grouped. The feature was intended for this use-case. However, now that you mention it, perhaps this should just be the default behavior and not even have that button. :)
|
Reporter | |
Comment 3•6 years ago
|
||
(In reply to Cameron Dawson [:camd] from comment #2)
There is a button on the toolbar to make these jobs visible. The "duplicates" button will prevent any job that has more than one occurrence in the platform from getting grouped. The feature was intended for this use-case. However, now that you mention it, perhaps this should just be the default behavior and not even have that button. :)
Ah, that could work for me.
I'm not sure over default, for performance runs, for example, you wouldn't necessarily want them all showing.
It's more when there are failed jobs, which we do show by default.
Always showing the successful jobs in that case would be ideal, but I'm fine with that button now you've pointed it out.
|
|
||
Comment 4•6 years ago
|
||
I'll close this for now. But if a better workflow opens up, please feel free to reopen. :)
Description
•