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

Issue 682253 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 682250



Sign in to add a comment

Improve failure-type grouping in SOM so we can group infra failures

Project Member Reported by katthomas@chromium.org, Jan 18 2017

Issue description

See go/burn-cit for more details

Identify the failure-type from the build logs, and then normalize it so it can be used by SOM to group failures.
* Could start with some classes of failure that are easy to pull out (stack trace, maybe?) and iteratively work towards a more sophisticated approach
* Or, SOM could ask “What should SOM look for in the step log to find other failures like these?" 



 
Description: Show this description
Blocking: 682250
Cc: katthomas@chromium.org zhangtiff@chromium.org seanmccullough@chromium.org
Components: Infra>CQ Infra>Sheriffing>SheriffOMatic Infra>Monitoring
Labels: -Pri-3 CQ-Reliability-and-Performance Pri-1
Status: Available (was: Untriaged)
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.
Labels: Milestone-Workflow
Adding a milestone for SoM triaging. :)
Labels: Hotlist-Infra-Failures
Components: -Infra>Monitoring
Components: -Infra>CQ
Status: Archived (was: Available)

Sign in to add a comment