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

Issue 598701 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

Android One Perf (2) not building on chromium.perf

Project Member Reported by sullivan@chromium.org, Mar 29 2016

Issue description

Link to buildbot status page:
https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%282%29

Two problems here:

1) No current builds and a huge list of pending builds
2) Last build had tons of failures, and was missing a device: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/2589

Can the trooper or someone from clank infra take a look? Not sure where to start.
 

Comment 1 by pschm...@google.com, Mar 29 2016

Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Mine too. 
Status: Started (was: Assigned)
The slave is back up and connected.   When you say it's missing a device you mean it should have 7 rather than 6 that is currently attached.  That 7th device was removed in https://bugs.chromium.org/p/chromium/issues/detail?id=585215 but no replacement was ever added back.

But we now have a couple of spares so I just added a 7th one back.  It will be visible starting with https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/2591

List of devices attached
AG860440G8CI0GC	device
AG8604420IC8CGC	device
AG860440GA0CIGC	device
AG8604420IG4GGC	device
AG8404EC08G2EGC	device
AG860440IC0G4GC	device
AG860440G6426GC	device




Looks like the new device is a "_b" type: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf%20(2)/builds/2591/steps/host_info/logs/json.output

      "device_names_list": [
        "google/4560MMX/4560MMX_sprout", 
        "google/4560MMX_b/4560MMX_b_sprout"
      ], 

Do you have any that aren't "_b"?
Issue 599425 has been merged into this issue.

Comment 5 by pschm...@google.com, Mar 31 2016

Forgot about this yesterday.  I'll go over to the lab in a bit to see if we have one.
I think you meant the other way.

No dice.   We only have 4560MMX_sprout (6 of them).    I have removed AG8404EC08G2EGC.

This is what is left on the slave:
Checking AG860440G6426GC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Checking AG8604420IG4GGC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Checking AG8604420IC8CGC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Checking AG860440G8CI0GC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Checking AG860440GA0CIGC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Checking AG860440IC0G4GC...
google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys
Status: Fixed (was: Started)
Closing as we cannot find a like replacement device.
Cc: rsch...@chromium.org
Ryan, can you help with finding a replacement?

Comment 9 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>Android
Labels: -Infra-Android
Components: Infra>Labs
Labels: -Infra-Labs

Sign in to add a comment