Link to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/4314
At least these look like device failures; the test results aren't available.
Typically:
/usr/bin/python /b/rr/tmp4bI41I/w/src/build/android/test_runner.py perf --print-step thread_times.key_mobile_sites_smooth --verbose --adb-path /b/rr/tmp4bI41I/w/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb --blacklist-file /b/rr/tmp4bI41I/w/src/out/bad_devices.json --enable-platform-mode --output-chartjson-data=/tmp/tmpF86GEF
I 0.003s Main command: /b/rr/tmp4bI41I/w/src/build/android/test_runner.py perf --print-step thread_times.key_mobile_sites_smooth --verbose --adb-path /b/rr/tmp4bI41I/w/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb --blacklist-file /b/rr/tmp4bI41I/w/src/out/bad_devices.json --enable-platform-mode --output-chartjson-data=/tmp/tmpF86GEF
E 0.003s Main File not found /b/rr/tmp4bI41I/w/src/out/step_results/thread_times.key_mobile_sites_smooth
E 0.003s Main Error occurred.
Comment 1 by oysteine@chromium.org
, Oct 26 2016Status: Duplicate (was: Unconfirmed)