[JBoss JIRA] (ARQ-1511) Wrong Android container identification in logs
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1511?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reopened ARQ-1511:
------------------------------------
> Wrong Android container identification in logs
> ----------------------------------------------
>
> Key: ARQ-1511
> URL: https://issues.jboss.org/browse/ARQ-1511
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: 1.0.0.Alpha2
>
>
> Despite the fact I have physical device attached and tests are running on that device, Droidium logs following:
> {code}
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.configuration.AndroidContainerConfiguration validate
> WARNING: Both "avdName" and "serialId" properties are defined, the device specified by "serialId" will get priority if connected.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.AndroidDeployableContainer start
> INFO: Starting the container Nexus4.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Initializing Android Debug Bridge.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 323ms.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl getPhysicalDevice
> INFO: Detected physical device with serial ID e8fd5c98.
> {code}
> *Starting the container Nexus4.* is a wrong log output.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1512) Droidum does not handle disconnect of a physical device correctly
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1512?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1512:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha2
(was: 1.0.0.Alpha2)
> Droidum does not handle disconnect of a physical device correctly
> -----------------------------------------------------------------
>
> Key: ARQ-1512
> URL: https://issues.jboss.org/browse/ARQ-1512
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: droidium_1.0.0.Alpha2
>
>
> *Given:*
> I have a device attached.
> *When:*
> I detach the device.
> *Expect:*
> Droidium will use avdName instead of serialId, if serialId is no longer available
> *Actual:*
> Droidium fails with:
> {code}
> org.arquillian.droidium.container.api.AndroidExecutionException: There are no devices on the Android bridge.
> at org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl.getPhysicalDevice(AndroidDeviceSelectorImpl.java:292)
> at org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl.selectDevice(AndroidDeviceSelectorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.arquillian.droidium.container.impl.AndroidBridgeConnector.initAndroidDebugBridge(AndroidBridgeConnector.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.arquillian.droidium.container.AndroidDeployableContainer.start(AndroidDeployableContainer.java:138)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1512) Droidum does not handle disconnect of a physical device correctly
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1512?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reopened ARQ-1512:
------------------------------------
> Droidum does not handle disconnect of a physical device correctly
> -----------------------------------------------------------------
>
> Key: ARQ-1512
> URL: https://issues.jboss.org/browse/ARQ-1512
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: 1.0.0.Alpha2
>
>
> *Given:*
> I have a device attached.
> *When:*
> I detach the device.
> *Expect:*
> Droidium will use avdName instead of serialId, if serialId is no longer available
> *Actual:*
> Droidium fails with:
> {code}
> org.arquillian.droidium.container.api.AndroidExecutionException: There are no devices on the Android bridge.
> at org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl.getPhysicalDevice(AndroidDeviceSelectorImpl.java:292)
> at org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl.selectDevice(AndroidDeviceSelectorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.arquillian.droidium.container.impl.AndroidBridgeConnector.initAndroidDebugBridge(AndroidBridgeConnector.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.arquillian.droidium.container.AndroidDeployableContainer.start(AndroidDeployableContainer.java:138)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1511) Wrong Android container identification in logs
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1511?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1511.
------------------------------------
Resolution: Done
> Wrong Android container identification in logs
> ----------------------------------------------
>
> Key: ARQ-1511
> URL: https://issues.jboss.org/browse/ARQ-1511
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: droidium_1.0.0.Alpha2
>
>
> Despite the fact I have physical device attached and tests are running on that device, Droidium logs following:
> {code}
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.configuration.AndroidContainerConfiguration validate
> WARNING: Both "avdName" and "serialId" properties are defined, the device specified by "serialId" will get priority if connected.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.AndroidDeployableContainer start
> INFO: Starting the container Nexus4.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Initializing Android Debug Bridge.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 323ms.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl getPhysicalDevice
> INFO: Detected physical device with serial ID e8fd5c98.
> {code}
> *Starting the container Nexus4.* is a wrong log output.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1511) Wrong Android container identification in logs
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1511?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1511:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha2
(was: 1.0.0.Alpha2)
> Wrong Android container identification in logs
> ----------------------------------------------
>
> Key: ARQ-1511
> URL: https://issues.jboss.org/browse/ARQ-1511
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: droidium_1.0.0.Alpha2
>
>
> Despite the fact I have physical device attached and tests are running on that device, Droidium logs following:
> {code}
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.configuration.AndroidContainerConfiguration validate
> WARNING: Both "avdName" and "serialId" properties are defined, the device specified by "serialId" will get priority if connected.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.AndroidDeployableContainer start
> INFO: Starting the container Nexus4.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Initializing Android Debug Bridge.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 323ms.
> Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl getPhysicalDevice
> INFO: Detected physical device with serial ID e8fd5c98.
> {code}
> *Starting the container Nexus4.* is a wrong log output.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1495.
------------------------------------
Resolution: Done
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: droidium_1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reopened ARQ-1495:
------------------------------------
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: 1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1495:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha2
(was: 1.0.0.Alpha2)
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: droidium_1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1506) Rename Droidium Container artifactId
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1506?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1506.
----------------------------------
> Rename Droidium Container artifactId
> ------------------------------------
>
> Key: ARQ-1506
> URL: https://issues.jboss.org/browse/ARQ-1506
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: droidium_1.0.0.Alpha2
>
>
> Current *org.arquillian.container:arquillian-droidium-container-depchain:pom* does not follow naming for other containers.
> It would be great to remove -depchain and make this non pom but jar artifact.
> Note that depchain does not make much sense here anyway. You either want the container or don't wont the container. Depchains are used to simplify usage of tools that are often extended and consists of many components.
> For the same matter, it might be reasonable to just rename *-impl artifact for the container to be the new depchain replacement, that is arquillian-droidium-container.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1506) Rename Droidium Container artifactId
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1506?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1506.
------------------------------------
Fix Version/s: 1.0.0.Alpha2
Resolution: Done
https://github.com/arquillian/arquillian-droidium/commit/61372a3fa091e651...
> Rename Droidium Container artifactId
> ------------------------------------
>
> Key: ARQ-1506
> URL: https://issues.jboss.org/browse/ARQ-1506
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: 1.0.0.Alpha2
>
>
> Current *org.arquillian.container:arquillian-droidium-container-depchain:pom* does not follow naming for other containers.
> It would be great to remove -depchain and make this non pom but jar artifact.
> Note that depchain does not make much sense here anyway. You either want the container or don't wont the container. Depchains are used to simplify usage of tools that are often extended and consists of many components.
> For the same matter, it might be reasonable to just rename *-impl artifact for the container to be the new depchain replacement, that is arquillian-droidium-container.
--
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
12 years, 6 months