[
https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.s...
]
Stefan Miklosovic commented on ARQ-1581:
----------------------------------------
This was automatically fixed by
https://code.google.com/p/android/issues/detail?id=60024
and Droidium has nothing to do here. From what I tested, when you specify ports like
--ports 12344,12346 the later one is made odd so it lowers the number by one, so it will
be 12344,12345. First number is console port, the second adb port. This is hard time for
Android Jenkins plugin since they generate these ports randomly so they need to lower that
random number to the non odd in order to get them rightly propagate to plugin specific
environment properties.
I hence mark this as resolved and wont fix.
Droidium does not work with remote emulators
--------------------------------------------
Key: ARQ-1581
URL:
https://issues.jboss.org/browse/ARQ-1581
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Karel Piwko
Assignee: Stefan Miklosovic
*When*:
I use Android Jenkins Plugin to start the device
*Then*:
It starts the emulator using remote syntax, that is including --port port1,port2
*Expect*:
Drodium will connect to already running emulator.
*Actual problem*:
AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from
adb devices. This results into Droidium trying to start emulator with the same name,
however this emulator is already started so event marking correct startup is never send
and test fails.
Output:
{code}
export ANDROID_ADB_SERVER_PORT=52892
[tester@fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test
./tools/android-sdk/platform-tools/adb devices
List of devices attached
localhost:46689 device
{code}
However, emulators are expected to be in format of emulator-XYZ.
Drodium should be able to modify the behavior to handle this correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira