[jboss-jira] [JBoss JIRA] (WFLY-3630) NonPersistentIntervalTimerManagementTestCase fails sometimes
Frank Langelage (JIRA)
issues at jboss.org
Tue Jul 15 10:22:30 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985227#comment-12985227 ]
Frank Langelage commented on WFLY-3630:
---------------------------------------
Running org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentIntervalTimerManagementTestCase
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 23.322 sec <<< FAILURE! - in org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentIntervalTimerManagementTestCase
testSuspendAndTrigger(org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentIntervalTimerManagementTestCase) Time elapsed: 7.051 sec <<< FAILURE!
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:148)
at org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentIntervalTimerManagementTestCase.testSuspendAndTrigger(NonPersistentIntervalTimerManagementTestCase.java:73)
> NonPersistentIntervalTimerManagementTestCase fails sometimes
> ------------------------------------------------------------
>
> Key: WFLY-3630
> URL: https://issues.jboss.org/browse/WFLY-3630
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 9.0.0.Alpha1
> Environment: Windows 7 SP1, Oracle JDK 1.7.0_60
> Reporter: Frank Langelage
> Assignee: Jason Greene
>
> Testcase org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentIntervalTimerManagementTestCase fails sometimes for me when running build with all tests on Windows machine. I never saw this failure on my Solaris box using the same JDK version. And somehow the appearance of the failure seem to be related to the execution time.
> Executing the testsuite during the day does not show me this error. Only in the very late evening / early morning hours the error appeared. (All related to Central European Summer time in my case.)
> I added some debug output an saw, that, in case of failure, after "activateTimer" the timer fires immediately so that there is one timeout too much then. The initial timeout time of the timer is passed, when it's suspended. When activated it seems to make good for the missed timeout sometimes.
> The persistent version of this testcase located in the same package with exactly same logic never fails for me.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list