New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 713418 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

bot affinity 6 is broken on chromium.perf/Android Nexus6 WebView Perf (2), affecting 5 tests

Project Member Reported by oysteine@chromium.org, Apr 19 2017

Issue description

bot affinity 6 is broken on chromium.perf/Android Nexus6 WebView Perf (2), affecting 5 tests

Builders failed on: 
- Android Nexus6 WebView Perf (2): 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf%20%282%29



 

Comment 1 by pschm...@google.com, Apr 19 2017

Cc: benhenry@chromium.org vhang@chromium.org
There are only 6 devices connected to this slave, that's why you only see device affinity {0..5}

We have no more spares and they are way old.  So I dunno.

Comment 2 by iannu...@google.com, Apr 19 2017

Cc: jbudorick@chromium.org martiniss@chromium.org
+ some maybe people ?
Possible dupe of issue 712677?
er, nvm given #1.
Owner: martiniss@chromium.org
Status: Assigned (was: Available)
Looks like that bot has always had 6 devices. https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf%20%282%29/builds/1830 is a build that ran all the tests on just the 6. Something changed so that it now expects to have 7.

r84f4f2585534a98a827fb79962b2d8325ed61ecb is most likely that change. Assigning to author.
Stephen - FYI - this is manual until we have a machine DB, but this is a list of all of the bots and hosts and what to expect: https://docs.google.com/spreadsheets/d/1ZpjJ1dmXhOVY6DfcCcDmPcjWD5wPy60nrjdKDN-ynhE/edit#gid=1129474336

If/when you make changes, please refer to this and/or attempt to update this.

Comment 7 by pschm...@google.com, Apr 28 2017

Cc: rnep...@chromium.org sullivan@chromium.org pschmidt@chromium.org
 Issue 716455  has been merged into this issue.
I have a spare n6 thats been collecting dust on my desk if we need one for this bot. We expect all the perf android bots to have 7 devices.

Comment 9 by dtu@chromium.org, May 2 2017

Issue 716684 has been merged into this issue.
Any updates? Several tests (including system health) haven't been able to run on this bot for a couple of weeks now.
 Issue 718963  has been merged into this issue.
ping?

If finding suitable devices is an issue, could be at least make the bot expect 6 devices (rather than 7)?

Comment 13 by vhang@chromium.org, May 17 2017

I was able to buy 10 new N6 phones and they have been delivered to b-lab.
ping.
Labels: Type-Bug
Ned, according to our proposal, we take this whole thing down. 

Vince - do we have backup N6s available right now?

Comment 16 by vhang@chromium.org, May 25 2017

We do.  Bought 10 recently.

Comment 17 by jo...@google.com, May 26 2017

 Issue 726873  has been merged into this issue.

Comment 18 by jo...@google.com, May 26 2017

Located some of these. Going to flash and attach one up to build113-b1 now.

Comment 19 by jo...@google.com, May 27 2017

New device flashed and attached, as well as replaced a dodgy hub + one cable.

List of devices attached 
ZX1G226FSX	device
ZX1G22LDV5	device
ZX1G22LGXS	device
ZX1G22FVN4	device
ZX1G22KX7H	device
ZX1G4238BJ	device
ZX1G22WXG7	device
Thanks! At least for system health, this bot is looking fine now.
Status: Fixed (was: Assigned)

Sign in to add a comment