Provide symbolized stack trace if an automated test crashes |
||
Issue descriptionIn bug 616380 , a ChromeOS test possibly caught a bug that resulted in a crash, but none of the logs captured a symbolized stack trace. It would be really helpful if CrOS test infrastructure was modified to capture such traces automatically. :)
,
Jun 6 2016
At the end of a test, Autotest will collect all crash dumps on the dut and try to symbolicate the dumps. For that issue, do you see the actual crash dump was collected in the test result?
,
Jun 7 2016
For this test run, I don't see a dmp file created but there was a tab Chrome crash. https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=307508281
,
Jun 7 2016
I can't find a job with the dmp file now but I have seen one failing job with the dmp file for the same test failure.
,
Mar 16 2018
Bulk closing Infra>Client>ChromeOS issues untouched in over a year. |
||
►
Sign in to add a comment |
||
Comment 1 by rohi...@chromium.org
, Jun 3 2016Components: Infra>Client>ChromeOS Test
Owner: dshi@chromium.org