Disable Android device discovery when testing CrOS |
|||||
Issue descriptionVersion: Multiple versions including ToT OS: Remote testing CrOS device from Linux host What steps will reproduce the problem? Non-deterministic. Occasionally cannot find adb even after it is claimed to be properly installed. What is the expected output? "adb devices" is executed, finds nothing, then test continues. What do you see instead? (WARNING) 2016-02-20 07:25:30,161 android_device.FindAllAvailableDevices:197 adb reported as present, but NoAdbError thrown: [Errno 2] No such file or directory https://bugs.chromium.org/p/chromium/issues/detail?id=567797 is probably not root caused as adb still can get installed but is not executable, but we can totally workaround this for CrOS testing by disabling the Android device discovery.
,
Apr 15 2016
If you specify a non-android browser, shouldn't this check be skipped?
,
Apr 16 2016
That's not quite how specifying browsers works. ie, "reference" could be an Android browser or a desktop one. But I agree that if the platform is specified as something non-android, we shouldn't be looking for Android devices. Unfortunately, the browser finder code is a bit of a mess and should be refactored to help avoid issues like this, but no one has had the time to do it afaik. I'd be super happy to advice/review a fix for that if someone wants to take it on. +eakuefner@ since he was talking about browser finder code recently.
,
Apr 25 2016
Fixed by https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/7ea5228763e4cd9d39e4c39c14d4ad1fdb5bc4ac
,
Apr 25 2016
,
Apr 26 2016
Ben, thanks for this fix but it also needs to be put in the the M-51 branch.
,
Jul 31 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bccheng@chromium.org
, Apr 15 2016