Description of problem: org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentIntervalTimerManagementTestCase#testSuspendAndTrigger fails occasionally with "Timer should fire twice! expected:<2> but was:<3>" Version-Release number of selected component (if applicable): 6.4.3.CP.CR1 How reproducible: 10%, with higher CPU load or slower machine Steps to Reproduce: 1. ./integration-tests.sh -Dts.noSmoke -Dts.basic -Dtest=PersistentIntervalTimerManagementTestCase Actual results: Timer should fire twice! expected:<2> but was:<3> java.lang.AssertionError: Timer should fire twice! expected:<2> but was:<3> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.jboss.as.test.integration.ejb.timerservice.mgmt.AbstractTimerManagementTestCase.testSuspendAndTrigger(AbstractTimerManagementTestCase.java:149) at org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentIntervalTimerManagementTestCase.testSuspendAndTrigger(PersistentIntervalTimerManagementTestCase.java:73) Expected results: No failures in test case.
Another case where this could fail, I'll create a new PR addressing this as well. java.lang.AssertionError: Timer should fire once! expected:<1> but was:<2> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.jboss.as.test.integration.ejb.timerservice.mgmt.AbstractTimerManagementTestCase.testSuspendAndTrigger(AbstractTimerManagementTestCase.java:146) at org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testSuspendAndTrigger(PersistentCalendarTimerManagementTestCase.java:73)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Verified with EAP 6.4.13.CP.CR2
Released with EAP 6.4.13 on Feb 02 2017.