Issue metadata
Sign in to add a comment
|
system_health.common_mobile and system_health.common_mobile.reference using wrong shard? |
||||||||||||||||||||||
Issue descriptionLink to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/4220 Tests on device affinity 6 are purple: /usr/bin/python /b/rr/tmplbJ1fV/w/src/build/android/test_runner.py perf --print-step system_health.common_mobile.reference --verbose --adb-path /b/rr/tmplbJ1fV/w/src/third_party/android_tools/sdk/platform-tools/adb --blacklist-file /b/rr/tmplbJ1fV/w/src/out/bad_devices.json --output-chartjson-data=/tmp/tmpjMae7S I 0.005s Main command: /b/rr/tmplbJ1fV/w/src/build/android/test_runner.py perf --print-step system_health.common_mobile.reference --verbose --adb-path /b/rr/tmplbJ1fV/w/src/third_party/android_tools/sdk/platform-tools/adb --blacklist-file /b/rr/tmplbJ1fV/w/src/out/bad_devices.json --output-chartjson-data=/tmp/tmpjMae7S E 0.005s Main File not found /b/rr/tmplbJ1fV/w/src/out/step_results/system_health.common_mobile.reference E 0.006s Main Error occurred. Traceback (most recent call last): File "/b/rr/tmplbJ1fV/w/src/build/android/test_runner.py", line 946, in main return RunTestsCommand(args) File "/b/rr/tmplbJ1fV/w/src/build/android/test_runner.py", line 766, in RunTestsCommand return RunTestsInPlatformMode(args) File "/b/rr/tmplbJ1fV/w/src/build/android/test_runner.py", line 834, in RunTestsInPlatformMode raw_results = test_run.RunTests() File "/b/rr/tmplbJ1fV/w/src/build/android/pylib/local/device/local_device_perf_test_run.py", line 498, in RunTests result_type = self._test_instance.PrintTestOutput() File "/b/rr/tmplbJ1fV/w/src/build/android/pylib/perf/perf_test_instance.py", line 124, in PrintTestOutput raise PersistentDataError('No data for test %s found.' % self._print_step) PersistentDataError: No data for test system_health.common_mobile.reference found.
,
Sep 15 2016
Couldn't seem to find what mapped to device affinity 6. Any idea what the device serial is?
,
Sep 15 2016
No, and I'm confused; I can only find references to six devices in any of the steps. Why are two tests trying to use a seventh?
,
Sep 15 2016
Does anyone know what's happening here?
,
Sep 15 2016
,
Sep 15 2016
vhang: I think the builder is missing an android one device, we got you some more of them a few weeks ago, would you be able to add one on? dtu, nednguyen: any ideas how device sharding works here? are the system_health tests pinned to the seventh device?
,
Sep 15 2016
The logic of sharding is in https://github.com/catapult-project/catapult/blob/master/telemetry/telemetry/benchmark_runner.py#L296 I looked at the log of "List Perf Tests " & found that telemetry is passed --num-shard=21, which is clearly a bug in the recipe. python -u /b/rr/tmplbJ1fV/w/src/tools/perf/run_benchmark list --browser android-chromium --json-output /tmp/tmp_udyu7.json --num-shards 21 --device AG860440G8CI0GC (https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/4220/steps/List%20Perf%20Tests/logs/stdio)
,
Sep 15 2016
We have spare phones. It will take a few hours to charge one up. I'll connect it to the host first thing in the morning.
,
Sep 16 2016
There are supposed to be 7 devices, so just looks like one is missing. --num-shards 21 is right, because there are 3 hosts * 7 devices each.
,
Sep 16 2016
build18-b1 is back to having 7 devices: List of devices attached AG860440G8AI2GC device AG860440IC0G4GC device AG860440GA0CIGC device AG8604420IG4GGC device AG860440G6426GC device AG860440G8CI0GC device AG8604420IC8CGC device
,
Sep 19 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jo...@google.com
, Sep 14 2016Status: Assigned (was: Untriaged)