New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 854680 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ nednguyen@chromium.org
eyaich@chromium.org
charliea@chromium.org
seanmccullough@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Sheriff-o-matic UI confusing with One Buildbot Step on perf builders

Project Member Reported by sullivan@chromium.org, Jun 20 2018 
I've been perfbot sheriff for two days. Yesterday, a story was failing on v8.browsing benchmarks, and I disabled it and associated a bug with the failure.

This morning I came in and saw that there was a "performance_test_suite failing on chromium.perf/linux-perf" failure associated with my bug, even though I had disabled the story. I clicked on the builder and there is a completely different problem--the step is failing but not that story. I re-associated the alert with  bug 854676 , but I think this might lead to a big regression in perfbot sheriffing.

We worked really hard to get the exact benchmark and story that are failing showing in sheriff-o-matic, and now it looks like all OBBS failures on a builder may be associated with the same bug? Does anyone know why?
Screen Shot 2018-06-20 at 1.38.38 PM.png
55.2 KB View Download

Comment 1 by eyaich@chromium.org, Jun 20 2018 

I am not sure why it would now correlate your bug with the new linux failure.  All I can guess is that the new failure started happening before the disable took place, so the bug was associated with the linux alert.  All errors on linux will be under one SOM step now.

Comment 2 by zhangtiff@chromium.org, Dec 18

Labels: Milestone-Data
Status: Available (was: Untriaged)
►

Sign in to add a comment