It was killed after timeout:

2/30 17:19:12.684 WARNI|        base_utils:0912| run process timeout (3600) fired on: python /tmp/chrome_root/src/tools/perf/run_benchmark --browser=cros-chrome --remote=chromeos2-row9-rack9-host7.cros --output-format=chartjson  page_cycler_v2.typical_25
12/30 17:19:18.700 DEBUG|telemetry_Crosperf:0179| Error occurred executing telemetry.

This is a major problem of toolchain team's nightly performance test so raising the priority.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/75187bce207199265e6a2e6b12bb390ade48f785

commit 75187bce207199265e6a2e6b12bb390ade48f785
Author: Ting-Yuan Huang <laszio@chromium.org>
Date: Sat Mar 18 05:00:42 2017

telemetry_Crosperf: Print telemetry logs

The indentation was incorrect and the logs only get printed when the
telemetry run succeeds.

BUG= chromium:678348 
TEST=Both successful and failed runs have telemetry logs.

Change-Id: Ifed629854a015d49fb02565c3552b4950dd042d1
Reviewed-on: https://chromium-review.googlesource.com/456483
Commit-Ready: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>

[modify] https://crrev.com/75187bce207199265e6a2e6b12bb390ade48f785/server/site_tests/telemetry_Crosperf/telemetry_Crosperf.py

no longer happens