Background
When a Pinpoint job fails, it posts a comment on the linked bug. Often, users don't click through to the Pinpoint UI to see what happened. Therefore, Pinpoint needs to plumb the error messages through to the user. Currently, Pinpoint parses the logs for Python stack traces.

Problem
We shouldn't rely on flaky parsing behavior. We also have no robust way to pull out error messages that don't have a stack trace, in cases like a nonexistent benchmark [1] or invalid arguments [2].

Solution
We'd like Telemetry to produce an output file containing structured results. Telemetry already produces a GTest-style file listing the passes/failures/skips, but it contains no error details. We can either expand the existing file format or add a new output file type.


[1] https://pinpoint-dot-chromeperf.appspot.com/job/14bb6286a40000
[2] https://pinpoint-dot-chromeperf.appspot.com/job/14a85420640000