New issue
Advanced search Search tips

Issue 825230 link

Starred by 1 user
Status: WontFix
Owner:
mmoss@chromium.org
Closed: Mar 2018
Cc:
etienneb@chromium.org
erikc...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Missing debug information on crash server

Project Member Reported by etienneb@chromium.org, Mar 23 2018 
I'm investigating a bug for a chrome slow-report trace: 0ecf74866d712b29

This trace is from chrome:
  Mac x64   version: 67.0.3369.0 


The trace failed to symbolized by our code.
It's failing while trying to fetch the symbols using crash API.

  Failed to get symbols for google chrome framework
    'Google Chrome Framework|D15709CFD21C3671BADF238B6940EF020' :
    (ResponseStatus.StatusCode:5) no data are available

  Failed to get symbols for google chrome canary
    'Google Chrome Canary|C98D140DDD7B31B8A4FDDE246B16E0310' :
    (ResponseStatus.StatusCode:5) no data are available

I look to the GSC drive and the breakpad file was generated and is valid. The data is not in our bigtable.

It seem to me that the file was not uploaded to our crash server.

Comment 1 by mmoss@chromium.org, Mar 26 2018 

That particular build was a fluke which failed before it got to the symbol upload step:

https://uberchromegw.corp.google.com/i/official.desktop/builders/mac64/builds/2749

Is it possible to test with a later build?

Comment 2 by etienneb@chromium.org, Mar 26 2018 

 > Is it possible to test with a later build?

I can test if that's frequent or not.

We are able to symbolize MAC trace, so it seems to be uploaded often.
I didn't look our frequent that step was failing.

Comment 3 by mmoss@chromium.org, Mar 26 2018 

it doesn't fail frequently at all (other people, including me, are definitely watching those builds). You just happened to pick a very rare version where this was broken.

Comment 4 by etienneb@chromium.org, Mar 28 2018

Status: WontFix (was: Untriaged)
I moved our log errors to our table and can confirm that was an glitch.
This is the only version failing.
The second case was in M65.

Let close this issue.
►

Sign in to add a comment