Bug 883452 - SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode failing
Summary: SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode failing
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER12
: 6.1.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-04 16:15 UTC by Anna Manukyan
Modified: 2025-02-10 03:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2257 0 Major Resolved SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode still randomly failing 2013-03-04 08:50:51 UTC

Description Anna Manukyan 2012-12-04 16:15:26 UTC
I've just run the Infinispan Testsuit for JDG 6.0.1.GA on RHEL 6.4_x86 - IBM JDK7, and the test is failing constantly (the interesting thing is that it hadn't fail on 64 bit system).

The log is:

testForceCommitOnOtherNode(org.infinispan.tx.recovery.admin.SimpleCacheRecoveryAdminTest) Time elapsed: 0.003 sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:480)
at org.testng.Assert.assertEquals(Assert.java:118)
at org.testng.Assert.assertEquals(Assert.java:365)
at org.testng.Assert.assertEquals(Assert.java:375)
at org.infinispan.tx.recovery.admin.SimpleCacheRecoveryAdminTest.assertInDoubtTxCount(SimpleCacheRecoveryAdminTest.java:214)
at org.infinispan.tx.recovery.admin.SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode(SimpleCacheRecoveryAdminTest.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1147)
at org.testng.TestRunner.privateRun(TestRunner.java:749)
at org.testng.TestRunner.run(TestRunner.java:600)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)
at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.lang.Thread.run(Thread.java:780)

Comment 2 Tristan Tarrant 2013-02-22 09:13:43 UTC
amanukya reports the issue hasn't happened recently, so it might be safe to assume it is resolved

Comment 3 JBoss JIRA Server 2013-03-04 08:50:32 UTC
Anna Manukyan <amanukya> updated the status of jira ISPN-2257 to Resolved

Comment 4 JBoss JIRA Server 2013-03-04 08:50:32 UTC
Anna Manukyan <amanukya> made a comment on jira ISPN-2257

The issue doesn't appear any more.

Comment 5 JBoss JIRA Server 2013-03-04 08:50:41 UTC
Anna Manukyan <amanukya> updated the status of jira ISPN-2257 to Reopened

Comment 6 JBoss JIRA Server 2013-03-04 08:50:52 UTC
Anna Manukyan <amanukya> updated the status of jira ISPN-2257 to Resolved

Comment 7 Anna Manukyan 2013-03-04 08:51:30 UTC
The issue doesn't appear any more. Is verified for JDG 6.1.0.ER12.

Comment 9 Red Hat Bugzilla 2025-02-10 03:27:05 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.