Catch IOError when reading chartjson results in test_runner.py

Catch IOError when reading chartjson results in test_runner.py

Right now, if the results aren't there, the entire sharded perf tests step fails. This doesn't fix the underlying issue, but at least allows the rest of the tests to run and makes it clearer which step failed.

With Patch: http://simonhatch0.mon.corp.google.com:8013/builders/Android%20Nexus7v2%20Perf/builds/593

Without: http://simonhatch0.mon.corp.google.com:8013/builders/Android%20Nexus7v2%20Perf/builds/591

BUG=498412
Committed: https://crrev.com/eca5b79197f9f2e8c15ea8e55477d424649b1cc9
Cr-Commit-Position: refs/heads/master@{#333593}

[shatch, 2015-06-09 19:52:21]

simonhatch@chromium.org changed reviewers:
+ jbudorick@chromium.org

[jbudorick, 2015-06-09 19:54:17]

This isn't going to solve the underlying problem, though it may allow
ShardedPerfTests to continue.

https://codereview.chromium.org/1176613002/diff/1/build/android/pylib/perf/te...
File build/android/pylib/perf/test_runner.py (right):

https://codereview.chromium.org/1176613002/diff/1/build/android/pylib/perf/te...
build/android/pylib/perf/test_runner.py:240: logging.error('Exception when
reading chartjson: %s', e)
logging.exception

[jbudorick, 2015-06-09 20:00:59]

https://codereview.chromium.org/1176613002/diff/20001/build/android/pylib/per...
File build/android/pylib/perf/test_runner.py (right):

https://codereview.chromium.org/1176613002/diff/20001/build/android/pylib/per...
build/android/pylib/perf/test_runner.py:240: logging.exception('Exception when
reading chartjson: %s', e)
logging.exception automatically logs the exception (and the trace), so you can
remove e.

[shatch, 2015-06-09 20:33:47]

https://codereview.chromium.org/1176613002/diff/20001/build/android/pylib/per...
File build/android/pylib/perf/test_runner.py (right):

https://codereview.chromium.org/1176613002/diff/20001/build/android/pylib/per...
build/android/pylib/perf/test_runner.py:240: logging.exception('Exception when
reading chartjson: %s', e)
On 2015/06/09 20:00:59, jbudorick wrote:
> logging.exception automatically logs the exception (and the trace), so you can
> remove e.

Done.

[jbudorick, 2015-06-09 20:42:11]

lgtm

[shatch, 2015-06-09 20:51:21]

The CQ bit was checked by simonhatch@chromium.org

[commit-bot: I haz the power, 2015-06-09 20:52:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1176613002/40001

[commit-bot: I haz the power, 2015-06-09 22:20:24]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-06-09 22:21:49]

Patchset 3 (id:??) landed as
https://crrev.com/eca5b79197f9f2e8c15ea8e55477d424649b1cc9
Cr-Commit-Position: refs/heads/master@{#333593}