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

Issue 840832 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 837855



Sign in to add a comment

Fine-grained flake detection for compile failures

Project Member Reported by liaoyuke@chromium.org, May 8 2018

Issue description

Right now, Chromium-try-flakes puts all compile failures into a single category, which doesn't really provide much insights. It would be better if some level of analysis can be done to identify exactly which target/file went wrong in the compilation process, and provide more actionable items to the Sheriffs/Troopers.
 

Comment 1 by st...@chromium.org, May 8 2018

https://luci-milo.appspot.com/buildbot/chromium/Android/84236

Those failed target/files are captured in the log named "json.output[ninja_info]" and the original errors are in "raw_io.output[failure_summary]".
Labels: flake-detection
Owner: ----
Status: Available (was: Assigned)
Chan, could you please triage this bug?

Sign in to add a comment