chromium.perf/Android Nexus Perf triggers tasks with unsupported dimensions |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com bot affinity 'build199-b7--device1', 'build199-b7--device2', 'build199-b7--device3', 'build199-b7--device4', 'build199-b7--device5', 'build199-b7--device6', 'build199-b7--device7', 'build200-b7--device1', 'build200-b7--device2', 'build200-b7--device3', 'build200-b7--device4', 'build200-b7--device5', 'build200-b7--device6', 'build200-b7--device7', 'build201-b7--device1', 'build201-b7--device2', 'build201-b7--device3', 'build201-b7--device4', 'build201-b7--device5', 'build201-b7--device6', 'build201-b7--device7' is broken on chromium.perf/Android Nexus5 Perf, affecting 159 tests Builders failed on: - Android Nexus5 Perf: https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5%20Perf
,
May 30 2018
The last build that didn't exhibit this error didn't specify device_os: https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5%20Perf/1790 Sample task: https://chrome-swarming.appspot.com/task?id=3dc5568312ca1b10
,
May 30 2018
a 7 character build ID seems like a typo in https://chromium-review.googlesource.com/c/chromium/src/+/1076670
,
May 30 2018
Last "good" build started on 2018-05-29 8:18 AM (PDT) First "bad" build started on 2018-05-29 1:51 PM (PDT) Something must have changed in between.
,
May 30 2018
Culprit CL: https://crrev.com/c/1076670 which introduced the bad dimension
,
May 30 2018
,
May 30 2018
https://chromium-review.googlesource.com/c/chromium/src/+/1079536 is in the queue to fix.
,
May 30 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c6b62211fe2d44688228883a751ff5282ac7d0b2 commit c6b62211fe2d44688228883a751ff5282ac7d0b2 Author: Emily Hanley <eyaich@google.com> Date: Wed May 30 18:42:24 2018 Updating device_os for Perf Nexus5 Bug:847926 Change-Id: I7fefb7fb9ed0e023c9e9ff0996c8bcdb4f4f04ee NOTRY=true # test covered by PRESUBMIT Change-Id: I7fefb7fb9ed0e023c9e9ff0996c8bcdb4f4f04ee Reviewed-on: https://chromium-review.googlesource.com/1079536 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Ashley Enstad <ashleymarie@chromium.org> Cr-Commit-Position: refs/heads/master@{#562931} [modify] https://crrev.com/c6b62211fe2d44688228883a751ff5282ac7d0b2/testing/buildbot/chromium.perf.json [modify] https://crrev.com/c6b62211fe2d44688228883a751ff5282ac7d0b2/tools/perf/core/perf_data_generator.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by sergeybe...@chromium.org
, May 30 2018Summary: chromium.perf/Android Nexus Perf triggers tasks with unsupported dimensions (was: bot affinity 'build199-b7--device1', 'build199-b7--device2', 'build199-b7--device3', 'build199-b7--device4', 'build199-b7--device5', 'build199-b7--device6', 'build199-b7--device7', 'build200-b7--device1', 'build200-b7--device2', 'build200-b7--device3', 'build200-b7--device4', 'build200-b7--device5', 'build200-b7--device6', 'build200-b7--device7', 'build201-b7--device1', 'build201-b7--device2', 'build201-b7--device3', 'build201-b7--device4', 'build201-b7--device5', 'build201-b7--device6', 'build201-b7--device7' is broken on chromium.perf/Android Nexus5 Perf, affecting 159 tests)