New issue
Advanced search Search tips

Issue 767503 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Improve visibility of mis-spelled builder names in EXPERIMENTAL= in tree status

Project Member Reported by ddavenp...@chromium.org, Sep 21 2017

Issue description

Currently this case is logged, but the log is not very visible and easy to miss.

Some ideas:
- Annotate an appropriate buildstep with an appropriate warning
- Surface this warning in sherrif-o-matic
 
I had previously indicated annotation, but that's the wrong terminology.  We want to add a build message in CIDB attached to the master build which indicates that slave X was marked as experimental (similar to how we indicate self destructed stages).

Within som_alerts_dispatcher.py, the function MapCIDBToSOMStatus uses the message subtype to ignore certain failures.

Cc: davidri...@chromium.org

Comment 3 by cindyb@chromium.org, May 31 2018

Hi, this bug has not been updated recently and remains untriaged. Please acknowledge the bug and provide status within two weeks (6/8/2018), or the bug will be closed. Thank you.
Owner: ----
AFAIK this is still an issue in that there is not very good feedback to sheriffs if the builder name specified in EXPERIMENTAL= is not great.

I don't think I will have the time to take this on, so unassigning.
Do you know what component this should move to, for triage? 
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
I suspect this will be obsoleted before it is fixed, but it belongs to CI.
Status: Archived (was: Untriaged)
We'll be replacing the entire concept of an EXPERIMENTAL builder in Tree Status in about 2 months.

Sign in to add a comment