[ https://issues.jboss.org/browse/WFLY-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147327#comment-13147327 ]
Romain Pelisse commented on WFLY-5641:
--------------------------------------
Sorry, for the delay on this one... I finally came around investigating it. I could reproduced a similar clean up issue with 10.0.0.CR4 and 10.0.0.CR5 but not with the current 'master' branch on Wildfly:
{code:java}
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 30.288 sec <<< FAILURE! - in org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
testFailoverFromRemoteClientWhenOneNodeGoesDown(org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase) Time elapsed: 29.965 sec <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb2-failover-test.jar
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
...
{code}
I would therefore suggest to retest this with the next release, as it seems to be fixed.
> Cleanup is not done properly after test have finished
> -----------------------------------------------------
>
> Key: WFLY-5641
> URL: https://issues.jboss.org/browse/WFLY-5641
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.CR4
> Reporter: Ivan Straka
> Assignee: Romain Pelisse
> Priority: Minor
>
> There are several tests failing because cleanup process was not done properly.
> This can be caused by ibmjdk1.8 that do not run test in different order. Therefore problem is shown.
> two exceptions:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-maven-rhel/lastCompletedBuild/jdk=ibm1.8,label_exp=EAP-RHEL7%20&&%20eap-sustaining/testReport/org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover/RemoteEJBClientStatefulBeanFailoverTestCase%28SYNC-tcp-extended%29/testFailoverFromRemoteClientWhenOneNodeGoesDown/
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-maven-rhel/lastCompletedBuild/jdk=ibm1.8,label_exp=EAP-RHEL7%20&&%20eap-sustaining/testReport/org.jboss.as.test.clustering.extended.ejb2.stateless/RemoteStatelessFailoverTestCase%28SYNC-tcp-extended%29/testFailoverOnUndeploySpecifiedByDescriptor/
> whole run:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-maven-rhel/3/testReport/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)