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

Issue 874187 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ mgiuca@chromium.org
chanli@chromium.org
█ robert...@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----

Blocking:
issue 666132



Sign in to add a comment

UI is not intuitive for analysis results of compile/test failures

Project Member Reported by st...@chromium.org, Aug 14 
Page URL: https://findit-for-me.appspot.com/waterfall/failure?url=https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20(dbg)(1)(32)/builds/51954#

 Description:
1. Links to Swarming rerun and try-job is not meaningful. Possible improvement could be:
   * Swarming rerun: "Failed 30 reruns at the build revision"
   * Try-job: "pass 30 reruns at r123, failed 30 reruns at r124"
2. Reasoning is not clear.

Comment 1 by mgiuca@chromium.org, Aug 20

Cc: mgiuca@chromium.org
Yep those sound useful.

When I originally reported this, I really wanted to know any additional information you can tell me (in plain language) about *why* FindIt blamed that CL. Specifically:

- If FindIt uses several different techniques to come to a conclusion, which of those (bisect? looking at the files changed by the CL? etc) was used to come to this conclusion. And,
- Specific to the answer to the previous question, any extra information that came from that technique (e.g., if a bisect, "pass 30 reruns at r123, failed 30 reruns at r124" would be great).
►

Sign in to add a comment