New issue
Advanced search Search tips

Issue 712808 link

Starred by 0 users
Status: Duplicate
Merged: issue 639171
Owner: ----
Closed: Dec 2017
Cc:
seanmccullough@chromium.org
martiniss@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

bug and comments are often stale

Project Member Reported by ojan@chromium.org, Apr 18 2017 
See the bug titles and the comments.

In either case, the bugs and comments are rarely relevant to the current failure because they're for entirely different tests. Whether it's leftover from previous failures or a bug in the mapping I can't tell.

This is true for basically all the bugs/comments I see, but here's a couple screenshots of examples.
Screenshot 2017-04-18 at 1.01.01 PM.png
103 KB View Download
Screenshot 2017-04-18 at 1.01.12 PM.png
155 KB View Download

Comment 1 by zhangtiff@chromium.org, Apr 18 2017 

This is a known issue and unfortunately comes from the way Sheriff-o-Matic generates keys for alerts (so sometimes alerts that are different can end up having the same key). 

Right now this is mitigated some by hiding/deleting old annotations. I could adjust that behavior to be a bit more aggressive. 

A more complete fix to this problem would probably require changing the way alerts are currently stored, which is on the roadmap (stretch goal for this quarter and probably next quarter if not this one).

Comment 2 by seanmccullough@chromium.org, Apr 19 2017

Labels: Milestone-UX
Status: Available (was: Untriaged)

Comment 3 by ojan@chromium.org, Apr 21 2017 

I think it's probably worth adjusting the beahvior to be more aggressive as a short-term fix. Basically every failure that happened had bugs that were wrong. I just started ignoring the bugs and comments for the most part.

Comment 4 by zhangtiff@chromium.org, Dec 5 2017

Mergedinto: 639171
Status: Duplicate (was: Available)
►

Sign in to add a comment