Sharded perf tests are failing at step 22
Link to most recent failing build:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/3311
Link to failing log:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/3311/steps/Sharded%20Perf%20Tests/logs/stdio
Seems to be an issue in the android test runner
Log output:
I 4932.092s Main Wrote device cache: /b/rr/tmpl9IKYg/w/src/out/Release/device_cache_3208cf5e05b2517f.json
E 4932.093s Main Unrecognized error occurred.
Traceback (most recent call last):
File "/b/rr/tmpl9IKYg/w/src/build/android/test_runner.py", line 995, in main
return RunTestsCommand(args)
File "/b/rr/tmpl9IKYg/w/src/build/android/test_runner.py", line 818, in RunTestsCommand
return RunTestsInPlatformMode(args)
File "/b/rr/tmpl9IKYg/w/src/build/android/test_runner.py", line 891, in RunTestsInPlatformMode
iteration_results.AddTestRunResults(r)
File "/b/rr/tmpl9IKYg/w/src/build/android/pylib/base/base_test_result.py", line 183, in AddTestRunResults
assert isinstance(results, TestRunResults)
AssertionError
step returned non-zero exit code: 1
@@@STEP_FAILURE@@@
Yeah, we are experimenting with a new perf test runner, adding some logging to see what is going on then will back out the new test runner until I can fix. I need some in the wild logging for this because I never saw it locally.
This bot remains flaky, but has been green on and off since build #3317.
#1 talks about backing out the new test, which I assumed happened in #2. Is there an ETA for getting the new version of Android test runner landed again?
I am hoping to land it again either today or tomorrow. Some of the failures related to it were around the less logging the new test runner has. Very long running tests were not outputting enough and the tests were timing out without output. I am adding a heartbeat message to stop this from happening.
Comment 1 by rnep...@chromium.org
, Jul 22 2016