February 2016 - jboss-jira - Jboss List Archives

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

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-611?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-611: --------------------------------- Assignee: (was: Ondrej Zizka) > 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: Ondřej 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 (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-902) Test framework for CLI-based tests can be very slow

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-902?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-902: --------------------------------- Assignee: (was: Ondrej Zizka) > Test framework for CLI-based tests can be very slow > --------------------------------------------------- > > Key: WFLY-902 > URL: https://issues.jboss.org/browse/WFLY-902 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: David Bosschaert > Priority: Minor > > The org.jboss.as.test.integration.management.base.AbstractCliTestBase provides a suitable API for testing CLI-based operations. However, running tests with a relatively large number of CLI operations can take a *long* time, seemingly much longer than necessary. This is probably related to the fact that CLIWrapper.readAllAsOpResult() method always seems to wait until the lineTimeout has expired. > Typically the WAIT_LINETIMEOUT value is used for this argument. Shortening the timeout is not an option as I have seen cases where a test would fail when run on a slow machine, but this only happens occasionally. > It would be *much* better if a timeout was not needed for this and the test would wait until a certain operation was finished. > This can be observed in org.jboss.as.test.integration.management.cli.JmsTestCase and I also experienced it when writing the org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-690) TS: XSLT doesn't work with JDK 7 and Xalan 2.7

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-690?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-690: --------------------------------- Assignee: (was: Ondrej Zizka) > TS: XSLT doesn't work with JDK 7 and Xalan 2.7 > ---------------------------------------------- > > Key: WFLY-690 > URL: https://issues.jboss.org/browse/WFLY-690 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Environment: Sun JDK 1.7.0, try mike.lab.bos.redhat.com > Reporter: Ondrej Zizka > Fix For: No Release > > > We are probably going to have problem with XSLT transformation in JDK 7: > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:xml-maven-plugin:1.0:transform (ts.config-as.ip) on project jboss-as-testsuite: Execution ts.config-as.ip of goal org.codehaus.mojo:xml-maven-plugin:1.0:transform failed: The value of param managementIPAddress must be a valid Java Object -> [Help 1] > {code} > This happened on Mike where I installed Sun JDK 1.7.0. > Here's some info: > http://dev-answers.blogspot.com/2006/07/xalan-parameter-must-be-valid-jav... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-774) Tests failing Intermittently on slow machines - iiop.basic.BasicIIOPInvocationTestCase

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-774?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-774: --------------------------------- Assignee: (was: Ondrej Zizka) > Tests failing Intermittently on slow machines - iiop.basic.BasicIIOPInvocationTestCase > -------------------------------------------------------------------------------------- > > Key: WFLY-774 > URL: https://issues.jboss.org/browse/WFLY-774 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondrej Zizka > > These tests fail intermittently on really slow machines. > To reproduce, try to run in EC2 on 32-bit "small" instance type. > https://jenkins-jbossqa.rhcloud.com/job/EAP6-EC2/61/#showFailuresLink > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testRemoteIIOPInvocation > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testHomeHandle > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testHandle > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testWrappedHandle > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testEjbMetadata > org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testIsIdentical -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1357) XSLT scripts for integration tests failing silently

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-1357?page=com.atlassian.jira.plugin.... ] Ondrej Zizka reassigned WFLY-1357: ---------------------------------- Assignee: (was: Ondrej Zizka) > XSLT scripts for integration tests failing silently > --------------------------------------------------- > > Key: WFLY-1357 > URL: https://issues.jboss.org/browse/WFLY-1357 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Environment: Wildfly integration tests > Reporter: Richard Achmatowicz > > We use XSLT scripts to build custom Wildfly distributions for testing. > Hard-coding of Wildfly subsystem namespace versions with no corresponding update to the scripts when schema versions change is causing XSLT scripts to be executed but silently not carry out the intended changes, resulting in broken test cases, of which no one is aware. > For example: > <xsl:stylesheet xmlns:jgroups="urn:jboss:domain:jgroups:1.1" > <xsl:template match="//jgroups:subsystem"> > // do something > </xsl:template> > <xsl:stylesheet> > will do nothing when executed against a 2.0 jgroups schema. > We need to have a general mechanism in place to work around the need to hardcode namespace versions when the namespace version is general and not specific. This needs to be applied to most XSLT scripts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1793) integration tests - allow modules to inherit properties variables

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-1793?page=com.atlassian.jira.plugin.... ] Ondrej Zizka reassigned WFLY-1793: ---------------------------------- Assignee: (was: Ondrej Zizka) > integration tests - allow modules to inherit properties variables > ----------------------------------------------------------------- > > Key: WFLY-1793 > URL: https://issues.jboss.org/browse/WFLY-1793 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: No Release > Reporter: Aleksandar Kostadinov > > Seems like surefire plug-in properties are not inherited by submodules by default. This is a problem as described in bz: > https://bugzilla.redhat.com/show_bug.cgi?id=990114 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-966) tests altering jboss.dist directory

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-966?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-966: --------------------------------- Assignee: (was: Ondrej Zizka) > tests altering jboss.dist directory > ----------------------------------- > > Key: WFLY-966 > URL: https://issues.jboss.org/browse/WFLY-966 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Aleksandar Kostadinov > > when running test suite with jboss.dost changed to a directory without write access two tests: > org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase.testAddRemoveCapabilities > org.jboss.as.test.integration.extension.remove.ExtensionRemoveTestCase.testAddAndRemoveExtension > With errors: > File could not be created: /usr/share/jbossas/bundles/org/jboss/test/testcap1343334290201/main/testcapabilitybundle.jar > Could not create /usr/share/jbossas/modules/extensionremovemodule/main > That means they are trying to alter the jboss distribution under testing which seems inconsistent with what the other tests do. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-934) test log should be placed to target directory

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-934?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-934: --------------------------------- Assignee: (was: Ondrej Zizka) > test log should be placed to target directory > --------------------------------------------- > > Key: WFLY-934 > URL: https://issues.jboss.org/browse/WFLY-934 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Peter Skopek > Priority: Minor > > test.log should be placed to target directory instead of target/workdir/target/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-797) jboss-as-arquillian-container-managed: the manager server keeps running if @RunAsClient testcase has been stopped. It should be set as a daemon process.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-797?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned WFLY-797: --------------------------------- Assignee: (was: Ondrej Zizka) > jboss-as-arquillian-container-managed: the manager server keeps running if @RunAsClient testcase has been stopped. It should be set as a daemon process. > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-797 > URL: https://issues.jboss.org/browse/WFLY-797 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Environment: JDK 1.6, Linux (Ubuntu 10.10), JBoss AS 7.1.1, IntelliJ 11.1.1 > Reporter: Geoffrey De Smet > > To reproduce with IntelliJ: > - Create a @RunAsClient testcase for a managed server. > - Put a breakpoint in it > - Debug the test case so it stops on the breakpoint, with IntelliJ > - Hit the "stop" button (a red square), also known as a soft kill. Note that this is not the "Exit" button, also known as a hard kill. > - Open your system monitor, notice that the managed server process is still running. > If you start the testcase again now, you get: > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. > To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:209) > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:70) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:113) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 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.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 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: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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 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: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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 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.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 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: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.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:76) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:182) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1056) QueryDataServiceIntegrationTest fails for MySQL5.5

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1056?page=com.atlassian.jira.plugi... ] Karel Suta reassigned DROOLS-1056: ---------------------------------- Assignee: Maciej Swiderski (was: Edson Tirelli) > QueryDataServiceIntegrationTest fails for MySQL5.5 > -------------------------------------------------- > > Key: DROOLS-1056 > URL: https://issues.jboss.org/browse/DROOLS-1056 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.0.Beta1 > Environment: version 6.4.0-SNAPSHOT > Reporter: Karel Suta > Assignee: Maciej Swiderski > Priority: Minor > Labels: reported-by-qe > Attachments: stacktrace.txt, stacktrace2.txt > > > QueryDataServiceIntegrationTest fails when it is run against MySQL 5.5 database. It is caused by errors in SQL expressions for queries. > See attachments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

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 February 2016