New issue
Advanced search Search tips

Issue 661458 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Wrong build blamed for webkit_tests failing on chromium.webkit/WebKit Win7 (dbg)

Project Member Reported by kjellander@chromium.org, Nov 2 2016

Issue description

Problem with Sheriff-o-Matic


During my sheriff shift today, SoM reported an error like this:
webkit_tests failing on chromium.webkit/WebKit Win7 (dbg)
Builders this step failed on: WebKit Win7 (dbg) [5 since first detection]
css3/filters/effect-reference-tile-hw.html ( Code Search )
chromium: 429071 - 429105 

It seems there's an off-by-one error in which build it blamed here. I checked the failures for builds #7950, #7951, #7952 and for them, only
paint/invalidation/compositing/should-not-clip-composited-overflow-scrolling-layer.html
paint/invalidation/compositing/should-not-clip-composited-viewport-scrolling-layer.html
fail.

The new failure "css3/filters/effect-reference-tile-hw.html" starts happening from this build:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%29/builds/7953

But the blame list (429071 - 429105) SoM/FindIt is reporting belongs to the next build:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%29/builds/7954
which is clearly wrong (all builds #7954+ has this test failing).

The correct blame list should be 429040-429070, which is essential for doing a good sheriff work.
 
Labels: Milestone-Workflow

Comment 2 by aga...@chromium.org, Nov 22 2016

Labels: -Infra-DX
Status: Available (was: Untriaged)
Seems like an odd thing for alerts-dispatcher to get wrong. Any thoughts, sean?
Nothing springs to mind immediately, but if this happens again we should run a-d manually to grab a snapshot so we can reproduce it.
Labels: Pri-2
If this is really a Pri-1, find an owner and update the priority.

This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 21 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)

Sign in to add a comment