-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
I don't know how common this is since TC didn't seem to recognize the individual test failure, so overall TC stats about the test are suspect, but...
https://ci.wildfly.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=449229
[05:32:52][Step 3/4] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.917 s <<< FAILURE! - in org.jboss.as.test.integration.messaging.jms.context.notclosinginjectedcontext.NotClosingInjectedContextTestCase [05:32:52][Step 3/4] [ERROR] testLeakingConnection(org.jboss.as.test.integration.messaging.jms.context.notclosinginjectedcontext.NotClosingInjectedContextTestCase) Time elapsed: 2.261 s <<< FAILURE! [05:32:52][Step 3/4] java.lang.AssertionError: There should be 2 received messages. expected:<2> but was:<0> [05:32:52][Step 3/4] at deployment.arquillian-service//org.junit.Assert.fail(Assert.java:89) [05:32:52][Step 3/4] at deployment.arquillian-service//org.junit.Assert.failNotEquals(Assert.java:835) [05:32:52][Step 3/4] at deployment.arquillian-service//org.junit.Assert.assertEquals(Assert.java:647) [05:32:52][Step 3/4] at deployment.NotClosingInjectedContextTestCase.war//org.jboss.as.test.integration.messaging.jms.context.notclosinginjectedcontext.NotClosingInjectedContextTestCase.testLeakingConnection(NotClosingInjectedContextTestCase.java:136)
I assume this is because the 2 second timeout to wait to receive a message elapsed for some environmental reason. We want a short timeout at the end (so we don't block waiting for a message that's not going to be sent) but there's no reason to use a short timeout for the messages we expect.
