New issue
Advanced search Search tips

Issue 882880 link

Starred by 1 user
Status: Duplicate
Merged: issue 879417
Owner: ----
Closed: Sep 20
Cc:
hinoka@chromium.org
seanmccullough@chromium.org
charliea@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

SOM still reporting alert for bot that's taken down

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Sep 11 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

It looks like SOM is reporting an alert for a bot that's now taken down. I suspect that the problem was that the last time that SOM queried the bot's status, it was broken. 

Now that the bot is offline, there's no successful status coming in to clear that old broken status and delete the alert.

The alert is "performance_test_suite on Android device gobo failing on chromium.perf".

Builders failed on: 
- android-go-perf: 
  https://ci.chromium.org/buildbot/chromium.perf/android-go-perf

Comment 1 by charliea@chromium.org, Sep 11

Cc: seanmccullough@chromium.org
Components: Infra>Sheriffing>SheriffOMatic
Adding SOM component. SOM team, is there anything we can do about this? This is on the perf sheriffing page.

Comment 2 by seanmccullough@chromium.org, Sep 11

Cc: hinoka@chromium.org
hinoka@ SoM just scans the builders it gets out of the build extract it gets from Milo's API.  Can milo remove this builder from the build extracts it returns?

Comment 3 by nednguyen@chromium.org, Sep 12 

Thanks for looking, Sean! It's worth noting that with the perf migration to LUCI, we also move from chromium project to chrome project to tighten our security model. This is a bit different from other LUCI migration.

Comment 4 by seanmccullough@google.com, Sep 20

Mergedinto: 879417
Status: Duplicate (was: Available)
Same root cause as https://bugs.chromium.org/p/chromium/issues/detail?id=879417
and since that's fixed, this should be too.
►

Sign in to add a comment