If you add stack trace, please add test coverage in https://code.google.com/p/chromium/codesearch#chromium/src/tools/perf/core/stacktrace_unittest.py

Jake:
a. Is this doable with your recent work getting stack traces on chromeos for failed autotests?
b. Any interest in taking this on?

It looks like the bug above is related to collecting non-Chrome stack traces. The work I did only related to Chrome crashes.

Feel free to assign the bug to me, but I probably won't be able to work on it for a few months.

fwiw, here is how Chrome crash stack trace collection works:

0. Start test
1. Chrome crashes, generates a stack dump
2. Test finishes
3. After-test server-side logic finds and uploads unsymoblized stack dumps files to a symbolization server that will then post the symbolized result inside the test results folder.

Nope, this is only for chrome crashes - telemetry doesn't care about any other processes on the device.

Re step 3 - test results folder in google storage or on the DUT?

I'll leave this assigned to bccheng@, but I imagine you will be available for advice and code reviews.

re #5: to google storage