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

Issue 709159 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Coding Error when analyzing debug logs

Reported by rrae...@flagstaffacademy.org, Apr 6 2017

Issue description

Chrome Version       : 56.0.2924.110 (Official Build) (32-bit)
URLs (if applicable) :
Other browsers tested:None - Chromebook
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1) Collect Debug Data
(2) Load file into google log analyser
(3) analyze log and wait for results

What is the expected result?
no error reported


What happens instead?
a message indicates a coding error and a bug should be reported

Please provide any additional information below. Attach a screenshot if
possible.
I was trying to update to version 57 but my device indicates it is up to date.  Logs show I have test HW instead of official SNOW hardware due to repair.
 
debug-logs_20170406-131209.tgz
157 KB Download
Components: Infra>CodeAnalysis
Labels: Needs-Milestone TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to analyzing log files using analyzer tool. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 8

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment