Sometimes a pinpoint try job might fail because e.g. some broken stories in the benchmark.

E.g.: https://pinpoint-dot-chromeperf.appspot.com/job/165233e4e40000

Even though many other stories did work correctly and provided some useful results, pinpoint will ignore completely the output of those runs. In particular it will not record the corresponding isolated hash for the output of those tasks.

Whether pinpoint should or not trust the results from such failed runs is perhaps debatable, but could we at least record the isolated hash so it's easy to get and view the results with pinpoint_cli?

(As a workaround, if the task id is there and the isolated output is not, I query the swarming server to get it; but it would be nice if we could avoid this.)