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

Issue 704318 link

Starred by 1 user
Status: Assigned
Owner:
semenzato@chromium.org
Cc:
snanda@chromium.org
█ keta...@chromium.org
hidehiko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

multiple reporting of the same error should be avoided

Project Member Reported by semenzato@chromium.org, Mar 22 2017 
It is difficult to identify root errors in test build logs, because some errors are recovered from, and logs can also collect multiple errors from steps running in parallel.  In many cases, the logs present multiple repetitions of the same log snippet, which further confuses the picture.  It would be useful to avoid this.

Comment 1 by semenzato@chromium.org, Mar 22 2017 

Forgot to mention: the repetitions can usually be identified by comparing the time stamps, but this is error-prone and time-consuming.

Comment 2 by keta...@chromium.org, Mar 22 2017

Labels: Logging-improv

Comment 3 by aut...@google.com, Mar 28 2017 

Can you provide some examples of this duplication?

Comment 4 by aut...@google.com, Apr 4 2017

Owner: semenzato@chromium.org
+ semenzato - do you have some examples of this?

Comment 5 by ayatane@chromium.org, Mar 14 2018

Status: Assigned (was: Untriaged)
This bug is Untriaged and very old.  Because it has an owner, the status will be set to assigned to avoid closing a bug someone is using.  If this bug still needs triage, change it back to Untriaged.
►

Sign in to add a comment