[jboss-jira] [JBoss JIRA] (WFLY-215) Clustering tests leave a hanging instance if they are run in opposite order

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12814304#comment-12814304 ] 

Radoslav Husar commented on WFLY-215:
-------------------------------------

Seems like something else is breaking it now, will try later:

{noformat}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 62.695 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.StatefulFailoverTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.648 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.LocalEJBClientFailoverTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.SlowUndeploymentRemoteFailoverTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.033 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateful.passivation.ClusterPassivationTestCase
Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 71.329 sec
Running org.jboss.as.test.clustering.cluster.ejb3.stateless.RemoteStatelessFailoverTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 68.688 sec
Running org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.857 sec
Running org.jboss.as.test.clustering.cluster.ejb3.descriptor.disable.DisableClusteredTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.079 sec
Running org.jboss.as.test.clustering.cluster.ejb3.security.FailoverWithSecurityTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 72.596 sec
Running org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 53.521 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 37.509 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.management.CacheTestCase
Tests run: 7, Failures: 2, Errors: 4, Skipped: 0, Time elapsed: 24.204 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.session.persistence.SessionClusterDbPersistenceTestCase
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 51.604 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 75.313 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.web.NonHaWebSessionPersistenceTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.959 sec
Running org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 42.493 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 32.747 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 91.496 sec <<< FAILURE!
Running org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase
...
{noformat}

Anyway, the branch is ready here:
https://github.com/rhusar/wildfly/compare/WFLY-215;testsuite_reverseorder?expand=1
                
> Clustering tests leave a hanging instance if they are run in opposite order
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-215
>                 URL: https://issues.jboss.org/browse/WFLY-215
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering, Test Suite
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>             Fix For: 8.0.0.CR1
>
>
> Interestingly, if the tests are run in the opposite order i.e. alphabetically, one server instance remains running and doesn't shut down.
> I have used a workaround for now
> {code}
> +                                    <!-- Force the order of tests -->
> +                                    <runOrder>reversealphabetical</runOrder>
> {code}

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