Issue metadata
Sign in to add a comment
|
Device offline on Nexus5(3) perf bot |
||||||||||||||||||||
Issue descriptionhttps://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29 Failing since February 8. Traceback (most recent call last): File "/b/c/b/Android_Nexus5_Perf__3_/src/build/android/test_runner.py", line 850, in main return RunTestsCommand(args) File "/b/c/b/Android_Nexus5_Perf__3_/src/build/android/test_runner.py", line 645, in RunTestsCommand return RunTestsInPlatformMode(args) File "/b/c/b/Android_Nexus5_Perf__3_/src/build/android/test_runner.py", line 745, in RunTestsInPlatformMode raw_results = test_run.RunTests() File "/b/c/b/Android_Nexus5_Perf__3_/src/build/android/pylib/local/device/local_device_perf_test_run.py", line 519, in RunTests result_type = self._test_instance.PrintTestOutput() File "/b/c/b/Android_Nexus5_Perf__3_/src/build/android/pylib/perf/perf_test_instance.py", line 128, in PrintTestOutput raise PersistentDataError('No data for test %s found.' % self._print_step) PersistentDataError: No data for test service_worker.service_worker_micro_benchmark found.
,
Feb 21 2017
That doesn't mean they are failing, it means they aren't running at all. The device is blacklisted in the device recovery, so no tests are run on it: Device Recovery: I 330.160s RecoverDevice(06a9c567003beeaf) Adding 06a9c567003beeaf to blacklist /b/c/b/Android_Nexus5_Perf__3_/src/out/bad_devices.json for reason: reboot_timeout Sharded Perf Tests W 1.432s device_shard_helper(4) Device 06a9c567003beeaf is not active. Will not create shard 4. Renaming and adding Infra>Labs component to reflect this.
,
Feb 21 2017
,
Feb 21 2017
Re-flashed 06a9c567003beeaf. Waiting for subsequent build to verify.
,
Feb 22 2017
Seeing lots of green now, after the re-flash. Thanks. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rsch...@chromium.org
, Feb 21 2017