[
https://issues.apache.org/jira/browse/CB-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard B Knoll updated CB-10671:
---------------------------------
Description:
Gathering logs fails for Android when there is more than one device connected.
That's fine, but for some reason a number of "ghost" emulators are hanging
around and causing {{adb devices}} to come up with more than one connected
emulator. The emulators are labelled as "host" rather than "device" in the
output and I have no idea what that is referring to (adb docs make no mention
of that as a possible value). Task manager confirms that no emulators are
actually running. This is either related to appium, CB-10510, or was always an
issue and is just now showing up because we stopped killing adb in medic-kill.
Running {{adb kill-server}} and {{adb start-server}} clears the host entries,
so that might be the quick fix.
Log Output for reference:
{code}
[MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] running:
[MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] adb devices
List of devices attached
emulator-5554 device
emulator-5572 host
emulator-5666 host
emulator-5668 host
emulator-5562 host
emulator-5656 host
[MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] FATAL: there must be exactly one
emulator/device attached
{code}
was:Gathering logs fails for Android when there is more than one device
connected. That's fine, but for some reason a number of "ghost" emulators are
hanging around and causing {{adb devices}} to come up with more than one
connected emulator. The emulators are labelled as "host" rather than "device"
in the output and I have no idea what that is referring to (adb docs make no
mention of that as a possible value). Task manager confirms that no emulators
are actually running. This is either related to appium, CB-10510, or was always
an issue and is just now showing up because we stopped killing adb in
medic-kill. Running {{adb kill-server}} and {{adb start-server}} clears the
host entries, so that might be the quick fix.
> Gathering Logs fails in android-win CI because of ghost emulators
> -----------------------------------------------------------------
>
> Key: CB-10671
> URL: https://issues.apache.org/jira/browse/CB-10671
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows 8.1
> Reporter: Richard B Knoll
> Labels: found-by-ci, triaged
>
> Gathering logs fails for Android when there is more than one device
> connected. That's fine, but for some reason a number of "ghost" emulators are
> hanging around and causing {{adb devices}} to come up with more than one
> connected emulator. The emulators are labelled as "host" rather than "device"
> in the output and I have no idea what that is referring to (adb docs make no
> mention of that as a possible value). Task manager confirms that no emulators
> are actually running. This is either related to appium, CB-10510, or was
> always an issue and is just now showing up because we stopped killing adb in
> medic-kill. Running {{adb kill-server}} and {{adb start-server}} clears the
> host entries, so that might be the quick fix.
> Log Output for reference:
> {code}
> [MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] running:
> [MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] adb devices
> List of devices attached
> emulator-5554 device
> emulator-5572 host
> emulator-5666 host
> emulator-5668 host
> emulator-5562 host
> emulator-5656 host
> [MEDIC LOG Mon, 22 Feb 2016 07:30:05 GMT] FATAL: there must be exactly one
> emulator/device attached
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
