We've scheduled the gaia-ui-tests on cedar on emulators, but they're currently failing with: 18:50:28 INFO - Traceback (most recent call last): 18:50:28 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/marionette_test.py", line 127, in run 18:50:28 INFO - self.setUp() 18:50:28 INFO - File "/builds/slave/test/gaia/tests/python/gaia-ui-tests/gaiatest/gaia_test.py", line 857, in setUp 18:50:28 INFO - self.get_device_manager(deviceSerial = self.marionette.device_serial)) 18:50:28 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/runner/mixins/b2g.py", line 19, in get_device_manager 18:50:28 INFO - self._device_manager = mozdevice.DeviceManagerADB(**kwargs) 18:50:28 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/mozdevice/devicemanagerADB.py", line 57, in __init__ 18:50:28 INFO - self._verifyADB() 18:50:28 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/mozdevice/devicemanagerADB.py", line 684, in _verifyADB 18:50:28 INFO - raise DMError("unable to execute ADB (%s): ensure Android SDK is installed and adb is in your $PATH" % err) 18:50:28 INFO - TEST-UNEXPECTED-FAIL | test_settings.py test_settings.TestSettings.test_get_all_settings | DMError: unable to execute ADB ([Errno 2] No such file or directory): ensure Android SDK is installed and adb is in your $PATH We should either use the copy of adb which is part of the emulator package, or update the PATH var to point to it when executing the mozharness script. Full log: https://tbpl.mozilla.org/php/getParsedLog.php?id=33918133&tree=Cedar&full=1#error0
The marionette runner doesn't have an --adbpath option, so if we did the former we'd have to add it.
Actually since Marionette is invoking the emulator here, it should be able to infer the correct location of adb, without having to pass it as a command-line parameter.
This problem disappeared at some point.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.