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

Issue 788968 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

NoDevicesError on lots of tests on a couple builders

Project Member Reported by ntfschr@chromium.org, Nov 28 2017

Issue description

Pretty sure troopers already saw this, but I'll file a bug anyway to make sure.

I see this on Lollipop Tablet Tester and Marshmallow Tablet Tester. A lot of tests (e.g. content_unittests, device_unittests, etc.) are failing with NoDevicesError.
 
Owner: bpastene@chromium.org
Status: Assigned (was: Untriaged)
I think because the devices on build42-b1 are really screwed up:
https://chromium-swarm.appspot.com/bot?id=build42-b1--device1
https://chromium-swarm.appspot.com/bot?id=build42-b1--device2
https://chromium-swarm.appspot.com/bot?id=build42-b1--device3
https://chromium-swarm.appspot.com/bot?id=build42-b1--device4

I'll see what I can find.

They were all unauthed with the host's adbkey but were still authed with the fleet's chrome_infra adb key. I have no idea how they managed to pull that off. And it turns out the swarming bot is smart enough to use both, but the tests only use the host key.

I went on and manually force auth'ed everything. They should be good to go now.
Cc: pasko@chromium.org
Thanks!

FYI pasko@ (in case there are still ~30 sheriff-o-matic notifications by the time you're in)
This should be fixed after #2. Feel free to reopen if you see it again.

Filed bug 789231 to prevent the weird auth failure.
Status: Fixed (was: Assigned)

Sign in to add a comment