January 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1183) Allow the use of non-blocking random number generators for deployments against WebLogic Servers

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1183?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1183: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Allow the use of non-blocking random number generators for deployments against WebLogic Servers > ----------------------------------------------------------------------------------------------- > > Key: ARQ-1183 > URL: https://issues.jboss.org/browse/ARQ-1183 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > The WLS container adapter forks a {{weblogic.Deployer}} task that runs in a separate JVM. This may result in timeouts on Unix/Linux machines where /dev/random does not provide sufficient entropy in a limited period of time. This eventually results in random and inexplicable failures during deployment or undeployment of archives when connecting to an AdminServer through a SSL channel. The stacktraces usually contain errors with the message "java.io.IOException: Stream closed.; No available router to destination". > Allow for configuring /dev/urandom as a PRNG source. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-784) The wlsHome property of the WebLogic containers should default to a pre-defined environment variable

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-784?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-784: ------------------------------ Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > The wlsHome property of the WebLogic containers should default to a pre-defined environment variable > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-784 > URL: https://issues.jboss.org/browse/ARQ-784 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha1, wls_1.0.0.Alpha2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > The `wlsHome` property does not have a default value at present, and users are expected to specify this in arquillian.xml; a system property could be used in arquillian.xml, but this would require Surefire or the test-execution environment to pass an existing environment variable as a system property. > It would useful to default this to the `WL_HOME` environment variable to preserve the intent of the property. However, we could consider using the `WLS_HOME` environment variable (this points to the `WL_HOME/server` directory) since all usages refer to resources in the server sub-directory. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1760) Replace the WebLogic.Deployer deployment mechanism with JMX for WLS 12.1.2 and higher

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1760?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1760: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Replace the WebLogic.Deployer deployment mechanism with JMX for WLS 12.1.2 and higher > ------------------------------------------------------------------------------------- > > Key: ARQ-1760 > URL: https://issues.jboss.org/browse/ARQ-1760 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > Replace the error prone WebLogic.Deployer based deployment mechanism with the JMX based deployer for WLS 12.1.2 (and higher version of WLS). The older deployment mechanism would however need to be in use for older versions of WLS since they do not have support for JMX based deployment of applications. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1898) Provide ExecutionServiceFactory instance by default

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1898?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1898. ------------------------------ Assignee: Karel Piwko Fix Version/s: spacelift_1.0.0.Alpha4 Resolution: Done Fixed in https://github.com/arquillian/arquillian-spacelift/commit/35ff36adf8b7d74... > Provide ExecutionServiceFactory instance by default > --------------------------------------------------- > > Key: ARQ-1898 > URL: https://issues.jboss.org/browse/ARQ-1898 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha4 > > > ExecutionServiceFactory should be instantiated by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1898) Provide ExecutionServiceFactory instance by default

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1898: -------------------------------- Summary: Provide ExecutionServiceFactory instance by default Key: ARQ-1898 URL: https://issues.jboss.org/browse/ARQ-1898 Project: Arquillian Issue Type: Feature Request Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha3 Reporter: Karel Piwko ExecutionServiceFactory should be instantiated by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1895) Implement video recorder for Droidium

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1895?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1895. ------------------------------------ Fix Version/s: droidium_1.0.0.Beta1 Resolution: Done > Implement video recorder for Droidium > ------------------------------------- > > Key: ARQ-1895 > URL: https://issues.jboss.org/browse/ARQ-1895 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha5 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > Implement recorder for Droidium based on video API of Arquillian Video Recorder. > The goal of this implementation is to record videos of Android phone itself via screenrecorder API in ddmlib since ddms 24.0.0 - aplicable for Android API 19+. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1897) Converting to time unit from miliseconds for CountDownWatch#timeLeft() is not necessary

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1897?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1897. ------------------------------------ Assignee: Stefan Miklosovic Fix Version/s: spacelift_1.0.0.Alpha4 Resolution: Done https://github.com/arquillian/arquillian-spacelift/commit/db95c47cafc9f90... > Converting to time unit from miliseconds for CountDownWatch#timeLeft() is not necessary > --------------------------------------------------------------------------------------- > > Key: ARQ-1897 > URL: https://issues.jboss.org/browse/ARQ-1897 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: spacelift_1.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1897) Converting to time unit from miliseconds for CountDownWatch#timeLeft() is not necessary

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created ARQ-1897: -------------------------------------- Summary: Converting to time unit from miliseconds for CountDownWatch#timeLeft() is not necessary Key: ARQ-1897 URL: https://issues.jboss.org/browse/ARQ-1897 Project: Arquillian Issue Type: Bug Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha3 Reporter: Stefan Miklosovic -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQRUSH-27) Implement change in structure: suite -> case* -> test* -> patterns+

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQRUSH-27?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQRUSH-27: --------------------------------- Assignee: (was: Lukáš Fryč) > Implement change in structure: suite -> case* -> test* -> patterns+ > ------------------------------------------------------------------- > > Key: ARQRUSH-27 > URL: https://issues.jboss.org/browse/ARQRUSH-27 > Project: Arquillian RushEye > Issue Type: Task > Components: Core, Manager > Reporter: Lukáš Fryč > Priority: Blocker > Fix For: 1.0.0.Alpha1 > > > To reflect test suites, Core should contain concept of {{case}} as container for tests. > {{test}} then forms a base for one comparison. > The new structure reflects how real functional tests maps to its output > * one functional test method = one case > * one functional test transition (image change) = one test > See ARQRUSH-26 > Support detection of changes in cases and tests (removals, additions, modifications) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction

by Michal Vanco (JIRA)

[ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.sy... ] Michal Vanco commented on ARQ-127: ---------------------------------- Hi Aslak (and others), today I came back to this issue after some time as it's still seems to be a critical thing which we would appreciate with arquillian-testng-stangalone library. I still used the same example just with updated dependencies. I tried some hacking at Arquillian.class and it seems like the usage of ThreadLocal is breaking this TestNG parallelism feature... {noformat} ... Running TestSuite BEFORE SUITE, runner:null Going to set test runner:org.jboss.arquillian.test.impl.EventTestRunnerAdaptor@266c6ce1, threadLocal:java.lang.ThreadLocal@18603b7c BEFORE CLASS, runner:null BEFORE CLASS, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER CLASS, runner:null AFTER CLASS, runner:null AFTER SUITE, runner:org.jboss.arquillian.test.impl.EventTestRunnerAdaptor@266c6ce1 {noformat} It's initialized once at the suite level, but none of the class/test methods are able to access it and it ends up with same message: {noformat} java.lang.IllegalStateException: No TestRunnerAdaptor found, @BeforeSuite has not been called at org.jboss.arquillian.testng.Arquillian.verifyTestRunnerAdaptorHasBeenSet(Arquillian.java:252) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:104) {noformat} [~aslak] - can you please confirm that there is any chance that Arquillian will be sometime able to handle this kind of parallelism (at least on class level)? Or maybe there is some quick hint you can provide... or should I just forget this requirement or workaround it at "ugly way"? Thanks a lot for your help! And I also thanks [~lfryc] for his help and support :) > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Ståle Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2015