March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-634) TS: Pass the path to docs/examples to the tests.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-634?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-634. ---------------------------- Resolution: Out of Date > TS: Pass the path to docs/examples to the tests. > ------------------------------------------------ > > Key: WFLY-634 > URL: https://issues.jboss.org/browse/WFLY-634 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In AS7, the path to the config file, passed in a system property, is only allowed to be a relative path. > In the testsuite, we would make use of absolute paths. > The reason is that we reuse the configs from docs/examples, and they change quite often, so having them in resources would be hardly maintainable. > However, docs/examples is not guaranteed to be always in the same place: E.g. for EAP, or for RPM-based installation of EAP it might end up in /var/docs or such. > I would like to pass some property from maven to the tests, but that results in absolute path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-611) TS: Test output is not stored in ...-output.txt

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-611?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-611. ---------------------------- Resolution: Out of Date > TS: Test output is not stored in ...-output.txt > ----------------------------------------------- > > Key: WFLY-611 > URL: https://issues.jboss.org/browse/WFLY-611 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondra Chaloupka > > ./integration-tests.sh clean install -Dtest=org.jboss.as.test.integration.ejb.async.* -Dintegration.module -Dbasic.integration.tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-634) TS: Pass the path to docs/examples to the tests.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-634?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reopened WFLY-634: ------------------------------ > TS: Pass the path to docs/examples to the tests. > ------------------------------------------------ > > Key: WFLY-634 > URL: https://issues.jboss.org/browse/WFLY-634 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In AS7, the path to the config file, passed in a system property, is only allowed to be a relative path. > In the testsuite, we would make use of absolute paths. > The reason is that we reuse the configs from docs/examples, and they change quite often, so having them in resources would be hardly maintainable. > However, docs/examples is not guaranteed to be always in the same place: E.g. for EAP, or for RPM-based installation of EAP it might end up in /var/docs or such. > I would like to pass some property from maven to the tests, but that results in absolute path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-611) TS: Test output is not stored in ...-output.txt

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-611?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reopened WFLY-611: ------------------------------ > TS: Test output is not stored in ...-output.txt > ----------------------------------------------- > > Key: WFLY-611 > URL: https://issues.jboss.org/browse/WFLY-611 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondra Chaloupka > > ./integration-tests.sh clean install -Dtest=org.jboss.as.test.integration.ejb.async.* -Dintegration.module -Dbasic.integration.tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-642) TS: -Dtest=*<something>* only matches one test per module.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-642?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-642. ---------------------------- Resolution: Out of Date > TS: -Dtest=*<something>* only matches one test per module. > ----------------------------------------------------------- > > Key: WFLY-642 > URL: https://issues.jboss.org/browse/WFLY-642 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Pavel Janousek > Assignee: Aslak Knutsen > > It seems like some regression. > When I've tried run like: > {code} > mvn3 clean install -Dts.basic '-Dtest=*.jaxrs.*' > {code} > I got this result: > {code} > [pjanouse@pjanouse testsuite]$ mvn3 clean install -Dts.basic '-Dtest=*.jaxrs.*' > Running org.jboss.as.test.smoke.jaxrs.JaxrsTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.689 sec > ... > ------ basic module: > Running org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.099 sec > ... > {code} > So you can see - Integration basic is invoked, but only TestCases org.jboss.as.test.smoke.jaxrs.JaxrsTestCase and org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCas were run although there are plenty of other TestCases fulfilled mask *\*.jaxrs.\** - many of them are localted in testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jaxrs/ + sub=dirs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-634) TS: Pass the path to docs/examples to the tests.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-634?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-634. ---------------------------- Resolution: Rejected > TS: Pass the path to docs/examples to the tests. > ------------------------------------------------ > > Key: WFLY-634 > URL: https://issues.jboss.org/browse/WFLY-634 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In AS7, the path to the config file, passed in a system property, is only allowed to be a relative path. > In the testsuite, we would make use of absolute paths. > The reason is that we reuse the configs from docs/examples, and they change quite often, so having them in resources would be hardly maintainable. > However, docs/examples is not guaranteed to be always in the same place: E.g. for EAP, or for RPM-based installation of EAP it might end up in /var/docs or such. > I would like to pass some property from maven to the tests, but that results in absolute path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-611) TS: Test output is not stored in ...-output.txt

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-611?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-611. ---------------------------- Resolution: Rejected > TS: Test output is not stored in ...-output.txt > ----------------------------------------------- > > Key: WFLY-611 > URL: https://issues.jboss.org/browse/WFLY-611 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondra Chaloupka > > ./integration-tests.sh clean install -Dtest=org.jboss.as.test.integration.ejb.async.* -Dintegration.module -Dbasic.integration.tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-625) TS: Multiple Surefire executions - FAILURE in one supresses successive.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-625?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-625. ---------------------------- Resolution: Rejected > TS: Multiple Surefire executions - FAILURE in one supresses successive. > ----------------------------------------------------------------------- > > Key: WFLY-625 > URL: https://issues.jboss.org/browse/WFLY-625 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > > Jason wrote that we can live with this for CR1; However having it fixed for EAP is important. > Work in progress at http://jira.codehaus.org/browse/SUREFIRE-803 . > John Casey keeps an eye on this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-982) Arquillian: IllegalStateException: standard-sockets -> http -> bound-port is undefined

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-982?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-982. ---------------------------- Resolution: Out of Date > Arquillian: IllegalStateException: standard-sockets -> http -> bound-port is undefined > -------------------------------------------------------------------------------------- > > Key: WFLY-982 > URL: https://issues.jboss.org/browse/WFLY-982 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Optional > > This happens sometimes in QA lab, probably due to slowness. > See https://hudson.qa.jboss.com/hudson/job/AS7-TS-valid-mvn-all-ipv6/56/testR... > {code} > java.lang.RuntimeException: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:222) > at org.jboss.as.arquillian.container.ManagementClient.getWebUri(ManagementClient.java:111) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:117) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:150) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:156) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:123) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:266) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:90) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:79) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:258) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:234) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined > at org.jboss.as.arquillian.container.ManagementClient.defined(ManagementClient.java:193) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:218) > ... 96 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1964) When controlling EAP 6 via Arquillian it sometimes starts to hang

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1964?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-1964. ----------------------------- Resolution: Out of Date > When controlling EAP 6 via Arquillian it sometimes starts to hang > ----------------------------------------------------------------- > > Key: WFLY-1964 > URL: https://issues.jboss.org/browse/WFLY-1964 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Radim Hatlapatka > Assignee: Andrew Rubinger > > See [ARQ-1464|https://issues.jboss.org/browse/ARQ-1464] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017