NoDevicesError on lots of tests on a couple builders |
|||
Issue descriptionPretty 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.
,
Nov 28 2017
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.
,
Nov 28 2017
Thanks! FYI pasko@ (in case there are still ~30 sheriff-o-matic notifications by the time you're in)
,
Nov 28 2017
This should be fixed after #2. Feel free to reopen if you see it again. Filed bug 789231 to prevent the weird auth failure.
,
Nov 28 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bpastene@chromium.org
, Nov 28 2017Status: Assigned (was: Untriaged)