I actually see this for a case with different stepnames as well (I think?). I'm marking this as P1. It makes it so I can't trust anything in sheriff-o-matic and need to click through to the buildbot pages to verify that it's actually a consistent failure.

This sounds like a bug in the step failure grouping logic. 

Is this still happening?  And if so, is it really a P1?  Our P1 turn around time shouldn't be >4 months ...

This is probably P2 instead of P1 though we do have some old P1 in Sheriff-o-Matic. The SoM Triage Rotation ( go/som-bug-triage ) tends to mostly focus on processing new bugs, and we don't tend to assign owners. 

Sean, what do you think about potentially amending our triage process a bit to help us have a better turnaround time on bugs? ie: maybe P1/P0 bugs should either get assigned an owner or deprioritized. 

Another thing I've thought is that it's a bit too easy for us to put milestones on bugs then forget they exist. I'm not sure how to best solve this, but it's something I think we can improve. I try to randomly look at go/som-issues every now and then but with almost 200 open SoM bugs going through the list can be overhwelming sometimes. 

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot