-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Recently CI has started showing pretty frequent cases of hundreds of tests failing in a job (typically 528), focused on the clustering testsuite. I've looked into a couple, e.g.
https://ci.wildfly.org/viewLog.html?buildId=349372&buildTypeId=WF_PullRequest_LinuxJdk17 and it looks like TwoConnectorsEJBFailoverTestCase is hanging in some way, leading to timeout of the surefire execution and subsequent chaos:
[19:25:07][Step 2/3] [INFO] Running org.jboss.as.test.clustering.cluster.ejb.remote.TwoConnectorsEJBFailoverTestCase [19:25:08][Step 2/3] org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_http [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollbackWithNoXAResourceEnlistment [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_http [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_remoteHttp [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_wildflyConfig [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_remoteHttp [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] directLookupFailure [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityNodeFailure [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_wildflyConfig [20:44:53][Step 2/3] [INFO] [20:44:53][Step 2/3] [INFO] Results: [20:44:53][Step 2/3] [INFO] [20:44:53][Step 2/3] [WARNING] Tests run: 35, Failures: 0, Errors: 0, Skipped: 5 [20:44:53][Step 2/3] [INFO] [20:44:53][Step 2/3] [ERROR] There was a timeout or other error in the fork
This is impacting a significant number of PRs so I am going to disable this test, referencing this issue. I'm setting the priority on this to Blocker due to the disabled test.
- clones
-
-
- Pull Request Sent
-
