Issue metadata
Sign in to add a comment
|
Android Chromedriver Tests fail on Waterfall because of all devices are in use |
||||||||||||||||||||||||
Issue descriptionTests are failing on the following reason: UnknownError: unknown error: All devices are in use (1 online) Oct 24 12:46 287861b16095946a4e12eb70c6e64a69fd00b243 failure #36892 Failed steps failed python_tests chromium failed python_tests chromium.run tests failed java_tests chromium failed java_tests chromium.run tests failed failure reason Oct 24 11:23 1d514493d6354b2d929e63ade437931cf82d6329 failure #36891 Failed steps failed python_tests chromium failed python_tests chromium.run tests failed java_tests chromium failed java_tests chromium.run tests failed failure reason
,
Oct 24 2017
Yes
,
Oct 24 2017
If so, given that this doesn't affect the other suites on the bot, I'm inclined to believe that this isn't an infra issue.
,
Oct 24 2017
This issue is affecting only the Chromium Android Build. It is an infra issue because all the Android devices are busy and they need to be available for the automation test run.
,
Oct 24 2017
It's not affecting the stable or beta suites on the same bot, though, hence my suggestion that, despite the log, it's not an infra problem. I've cc'ed kereliuk and johnchen to get their opinions on it.
,
Oct 24 2017
My guess is the Android device attached to the bot is in some kind of bad state, and needs to be reset. Is that something that can be done by the lab? Thanks.
,
Oct 24 2017
If that were the case -- vs a src/ side change that broke something -- I would expect to see *all* of the suites failing?
,
Oct 24 2017
I thought all tests were failing, but now I see some tests succeeded. I'll investigate further.
,
Oct 26 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jbudorick@chromium.org
, Oct 24 2017