Bug 876967 - Test StateTransferCacheLoaderFunctionalTest(StateTransferFunctionalTest) tests fail randomly
Summary: Test StateTransferCacheLoaderFunctionalTest(StateTransferFunctionalTest) test...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: TestSuite
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER4
: 6.5.0
Assignee: Martin Gencur
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 994439
TreeView+ depends on / blocked
 
Reported: 2012-11-15 11:55 UTC by Anna Manukyan
Modified: 2025-02-10 03:26 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 994439 (view as bug list)
Environment:
Last Closed: 2025-02-10 03:26:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2522 0 Major Resolved The org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest (StateTransferFunctionTest) tests fail periodica... 2017-01-17 12:14:20 UTC

Comment 3 Tomas Sykora 2015-02-17 14:27:11 UTC
Excavating this old one for JDG 6.5. 

It fails occasionally with approx 90 % success rate.

Failed 3 times in the last 30 runs. Stability: 90 %
Error Message

Incorrect value for key a_b_name expected:<JOE> but was:<null>

Stacktrace

java.lang.AssertionError: Incorrect value for key a_b_name expected:<JOE> but was:<null>
	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.infinispan.statetransfer.StateTransferFunctionalTest.verifyInitialData(StateTransferFunctionalTest.java:336)
	at org.infinispan.statetransfer.StateTransferFunctionalTest.writingThreadTest(StateTransferFunctionalTest.java:370)
	at org.infinispan.statetransfer.StateTransferFunctionalTest.testSTWithWritingNonTxThread(StateTransferFunctionalTest.java:255)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
	at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

Standard Output

[testng-StateTransferFunctionalTest] Test testSTWithWritingNonTxThread(org.infinispan.statetransfer.StateTransferFunctionalTest) failed.
Test suite progress: tests succeeded: 599, failed: 1, skipped: 0.

Comment 4 Tomas Sykora 2015-02-17 14:34:23 UTC
Related failure:

org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest.testSTWithWritingNonTxThread

Error Message

Method org.testng.internal.TestNGMethod.testSTWithWritingNonTxThread() didn't finish within the time-out 120000

Stacktrace

org.testng.internal.thread.ThreadTimeoutException: Method org.testng.internal.TestNGMethod.testSTWithWritingNonTxThread() didn't finish within the time-out 120000

Standard Output

[testng-StateTransferCacheLoaderFunctionalTest] Test testSTWithWritingNonTxThread(org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest) failed.
Test suite progress: tests succeeded: 1361, failed: 3, skipped: 0.

Maybe increasing time out would help? Not sure, will try.

Comment 5 Sebastian Łaskawiec 2015-02-19 08:39:55 UTC
Test ignored by PR: https://github.com/infinispan/jdg/pull/506

Comment 9 Red Hat Bugzilla 2025-02-10 03:26:57 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.