[JBoss JIRA] (ARQ-1440) Performance drops > 300%
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak resolved ARQ-1440.
---------------------------------
Resolution: Done
> Performance drops > 300%
> ------------------------
>
> Key: ARQ-1440
> URL: https://issues.jboss.org/browse/ARQ-1440
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6
> Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3
> Reporter: Noah White
> Assignee: Bartosz Majsak
> Priority: Critical
> Fix For: persistence_1.0.0.next
>
>
> I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment.
> For example one test which took 13s to run in the old environment now takes 44s.
> This slow down only seems to affect tests which use the persistence extension.
> Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests.
--
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
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1534:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha5
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> 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
> Fix For: droidium_1.0.0.Alpha5
>
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
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
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1534:
-----------------------------------
Comment: was deleted
(was: It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly resolve this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore.)
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> 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
> Fix For: droidium_1.0.0.Alpha5
>
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
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
[JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large
by Alex Soto (JIRA)
[ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.s... ]
Alex Soto commented on ARQ-1685:
--------------------------------
I completely agree that the first option is the best one. Moreover values like height and size could be take in consideration.
> Allow user to define when a screenshot is large
> -----------------------------------------------
>
> Key: ARQ-1685
> URL: https://issues.jboss.org/browse/ARQ-1685
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Reporter: Alex Soto
> Assignee: Stefan Miklosovic
> Priority: Minor
>
> In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not.
--
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
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1534.
------------------------------------
Resolution: Done
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> 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
> Fix For: droidium_1.0.0.Alpha5
>
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
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
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1534:
----------------------------------------
https://github.com/arquillian/arquillian-droidium/commit/51d5d96713629031...
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> 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
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
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
[JBoss JIRA] (ARQ-1557) Align undeployment logic in a proper Arquillian way
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1557?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1557:
--------------------------------------
Assignee: Stefan Miklosovic
> Align undeployment logic in a proper Arquillian way
> ---------------------------------------------------
>
> Key: ARQ-1557
> URL: https://issues.jboss.org/browse/ARQ-1557
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Attachments: brainstorming.jpg
>
>
> Right now, undeployment logic for Droidium is bound to observer which observes with precedence -100 on AfterClass event in order to be sure that this observer will be treated as the latest one.
> Right now, we have to be sure that undeployment logic is treated lastly in AfterClass since Arquillian Drone destroys WebDriver instances in AfterClass as well and the destruction of WebDriver instance, in our case, means that Selendroid server will be uninstalled from Android device.
> Since the destruction of WebDriver instance itself is executed randomly in AfterClass regarding of execution time, we can not do undeployment of APKs on UnDeployDeployment event because when doing so, uninstallation of instrumented APK automatically kills Selendroid server process as well so that in turn means that subsequent trying to destroy WebDriver instance fails since Selendroid server is not running anymore and Drone talks to nobody.
> To be sure that all Selendroid servers are uninstalled so we can proceed with the uninstallation of deployments, where it should be done, there has to be a guarantee that all WebDriver instances were already destroyed.
> The solution here seems to be quite simple - we put some positive precedence for DroneDestructor (1) however by doing so, it could cause some backward compatibility issues with Drone extension.
> (1) https://github.com/arquillian/arquillian-extension-drone/blob/master/dron...
--
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
[JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators
by Stefan Miklosovic (JIRA)
[ 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
12 years
[JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1581.
------------------------------------
Resolution: Won't Fix
It was automatically resolved by https://code.google.com/p/android/issues/detail?id=60024
> 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
12 years