Also show bugs for old runs. |
|||
Issue descriptionCurrently the behavior in go/som is: Build passed on run 1 Build failed on run 2 (Somebody filed a bug and linked the bug to this failed run) Then here come another failed run 3, then on go/som ui, it doesn't show anything about bug filed for run 2. So sometimes people will investigate run 3 again and not aware of there was a bug for run 2 already. This is confusing since actually in most case, it could be same bug in run 2. It's better change ui to show all bugs filed after latest passed runs so it's easy to know what happened.
,
May 7 2018
To clarify: Is this the exact same failing builder and build step (and same failing test, if it's a test step) in builds 2 and 3, where you've seen this behavior?
,
May 7 2018
Re #2, to tell the truth, I think it should be the same builder and failure reason. But I can't make sure it's exactly same failing test since I don't have link to those failures now and can't confirm.
,
May 22 2018
,
Aug 23
|
|||
►
Sign in to add a comment |
|||
Comment 1 by gu...@chromium.org
, Apr 18 2018