[
https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin....
]
Radoslav Husar reopened WFLY-3248:
----------------------------------
Assignee: Paul Ferraro (was: Radoslav Husar)
I have rerun the tests and all the async tests still actually fail horribly. Any chance
you omitted the {{-DextendedTests}} parameters for the testsuite run?
The failures seem to indicate timing issues.
{noformat}
StatefulFailoverTestCase.noFailover:134 expected:<1> but was:<0>
StatefulFailoverTestCase.simpleFailover:152->failover:211 expected:<9> but
was:<7>
CdiFailoverTestCase.testGracefulUndeployFailover:123->testFailoverOnUndeploy:195
expected:<9> but was:<7>
CdiFailoverTestCase.testGracefulSimpleFailover:101->testFailoverOnShutdown:137->queryCount:219
expected:<200> but was:<500>
SharedSessionFailoverTestCase.test:125 expected:<3> but was:<2>
CoarseSessionExpirationTestCase>SessionExpirationTestCase.test:100 null
FineSessionExpirationTestCase>SessionExpirationTestCase.test:152 expected:<[2]>
but was:<[1]>
ClusteredSingleSignOnTestCase.testNoAuthSingleSignOn:143 Get of
http://127.0.0.1:8180//war2/index.html redirected to login page
{noformat}
Removing ViewChangeListener* broke the extended clustering testsuite
--------------------------------------------------------------------
Key: WFLY-3248
URL:
https://issues.jboss.org/browse/WFLY-3248
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Test Suite
Affects Versions: 8.0.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 9.0.0.Beta1
What we did a while back, we made the sync-tcp the default configuration for running the
clustering tests. However, we kept a extended testsuite with other combinations and other
unimportant clustering tests.
The async combinations partly relied on the ViewChangeListener* mechanisms. This was not
detected earlier because this part of TS is not run by default on the CI.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)