New issue
Advanced search Search tips

Issue 851534 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

bot affinity 'build192-b7--device3', 'build192-b7--device6', 'build193-b7--device6' is broken on chromium.perf/Android One Perf, affecting 32 tests

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jun 11 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

bot affinity 'build192-b7--device3', 'build192-b7--device6', 'build193-b7--device6' is broken on chromium.perf/Android One Perf, affecting 32 tests

Builders failed on: 
- Android One Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Android%20One%20Perf
 
Components: Infra>Labs Speed>Benchmarks>Waterfall
Labels: -Infra-Troopers -Pri-2 OS-Android Pri-1
Infra>Labs, could you please check on these devices? They seem to be down.

Comment 2 by vhang@chromium.org, Jun 12 2018

Owner: vhang@chromium.org
Status: Assigned (was: Available)

Comment 3 by vhang@chromium.org, Jun 12 2018

Status: Fixed (was: Assigned)
All 3 devices has been rebooted.  Please reopen if this is still a problem.
Thanks Vince!
Status: Assigned (was: Fixed)
I'm still seeing issues in the most recent build:
https://ci.chromium.org/buildbot/chromium.perf/Android%20One%20Perf/1648

build192-b7--device3
build192-b7--device6
build193-b7--device6

Comment 6 by vhang@chromium.org, Jun 19 2018

Owner: jo...@chromium.org

Comment 7 by jo...@chromium.org, Jun 19 2018

Cc: vhang@chromium.org bpastene@chromium.org
The devices all appear online/healthing, but looking closer:

build192-b7--device3, build192-b7--device6 versions don't seem to match their counterparts:

build192-b7--device1 LMY47W
build192-b7--device2 LMY47W
build192-b7--device3 LMY48Y
build192-b7--device4 LMY47W
build192-b7--device5 LMY47W
build192-b7--device6 LMY48Y
build192-b7--device7 LMY47W

And the same goes for build193-b7--device6

build193-b7--device1 LMY47W
build193-b7--device2 LMY47W
build193-b7--device3 LMY47W
build193-b7--device4 LMY47W
build193-b7--device5 LMY47W
build193-b7--device6 LMY47X
build193-b7--device7 LMY47W

My guess is, because the dimension don't match, they are reporting as EXPIRED (lack of capacity) and failing. Does this sound plausible? If so we can work on re-flashing to normalize the versions here.

Thanks.

Cc: perezju@chromium.org
Hi John, we would want all these devices to be LMY47W

Comment 9 by jo...@google.com, Jun 19 2018

Thanks for confirming. We'll make it so.

Comment 10 by jo...@chromium.org, Jun 20 2018

Status: Fixed (was: Assigned)
Re-flashed the outliers. Hopefully this should fix the capacity issue. Please re-open if not. Thanks,

build192-b7--device1 LMY47W
build192-b7--device2 LMY47W
build192-b7--device3 LMY47W
build192-b7--device4 LMY47W
build192-b7--device5 LMY47W
build192-b7--device6 LMY47W
build192-b7--device7 LMY47W

build193-b7--device1 LMY47W 
build193-b7--device2 LMY47W
build193-b7--device3 LMY47W
build193-b7--device4 LMY47W
build193-b7--device5 LMY47W
build193-b7--device6 LMY47W
build193-b7--device7 LMY47W

Sign in to add a comment