Autotest chrome crashes are not symbolized |
||||
Issue descriptionExample: https://stainless.corp.google.com/browse/chromeos-autotest-results/227131535-chromeos-test/chromeos4-row13-rack5-host7/debug/ The chrome .dmp.txt files are empty: chrome.20180814.005353.13609.dmp.txt This broke sometime in the last week. It's a big problem for me -- the amount of extra work to pull a minidump and manually symbolize is major impediment to my ability to scan for new chrome crashes. +gardeners / sheriffs
,
Sep 10
I don't *think* this is a bug in the test infra, because the code for the copying the files over is just a dumb file copy. Is this definitely not a chrome or chromeos issue?
,
Sep 11
It looks like the devserver is responsible for symbolizing. guocb, have you looked as this part of the devserver?
,
Oct 5
,
Oct 5
This problem seems to come and go. Right now it's working. |
||||
►
Sign in to add a comment |
||||
Comment 1 by lannm@google.com
, Sep 10