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

Issue 821518 link

Starred by 1 user
Status: Fixed
Owner:
█ pschmidt@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Cc:
charliea@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

bot affinity 'build18-b1' (all devices) is broken on chromium.perf/Android One Perf, affecting 62 tests

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Mar 13 2018 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@google.com

bot affinity 'build18-b1--device1', 'build18-b1--device2', 'build18-b1--device3', 'build18-b1--device4', 'build18-b1--device5', 'build18-b1--device6', 'build18-b1--device7' is broken on chromium.perf/Android One Perf, affecting 62 tests

Builders failed on: 
- Android One Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf

Comment 1 by charliea@chromium.org, Mar 13 2018

Cc: -charliea@google.com charliea@chromium.org
Components: Infra>Labs
Infra>Labs, could you please take a look and see if there's anything that looks wrong with build18-b1, a Linux host hooked up to 7 Android One phones? It looks like no tests are successfully running on it.

Comment 2 by pschm...@google.com, Mar 13 2018

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

Comment 3 by pschm...@google.com, Mar 13 2018 

lsusb on build18-b1 just hangs.  Noticed that two battor's were not powered up.  Replaced their usb isolators and now they work.

Ended up power cycling the host to get things back up.

Comment 4 by charliea@chromium.org, Mar 13 2018 

Hmmm... that's not a great sign. Thanks for looking into that Peter.

Comment 5 by charliea@chromium.org, Mar 16 2018

Status: Fixed (was: Assigned)
Tha
►

Sign in to add a comment