[infinispan-issues] [JBoss JIRA] (ISPN-2354) AsyncStoreFunctionalTest fails intermittently

Sanne Grinovero (JIRA) jira-events at lists.jboss.org
Fri Nov 2 06:26:18 EDT 2012


    [ https://issues.jboss.org/browse/ISPN-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731118#comment-12731118 ] 

Sanne Grinovero commented on ISPN-2354:
---------------------------------------

I still have ISPN-2046 failing, which makes me think AsyncStore is still not 100% reliable. I'll be making a new stress test over the weekend to isolate the problem from Lucene.
                
> AsyncStoreFunctionalTest fails intermittently
> ---------------------------------------------
>
>                 Key: ISPN-2354
>                 URL: https://issues.jboss.org/browse/ISPN-2354
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 5.2.0.Alpha4
>            Reporter: Dan Berindei
>            Assignee: Galder Zamarreño
>              Labels: testsuite_stability
>             Fix For: 6.0.0.Final
>
>
> AsyncStoreFunctionalTest sometimes fails with this assertion error:
> {noformat}
> 14:49:46,380 ERROR (testng-AsyncStoreFunctionalTest:) [UnitTestTestNGListener] Test testGetAfterRemove(org.infinispan.loaders.decorators.AsyncStoreFunctionalTest) failed.
> java.lang.AssertionError: Keys not empty: [1]
> 	at org.testng.AssertJUnit.fail(AssertJUnit.java:57)
> 	at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:22)
> 	at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest$3.call(AsyncStoreFunctionalTest.java:211)
> 	at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1252)
> 	at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest.testGetAfterRemove(AsyncStoreFunctionalTest.java:165)
> 	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:601)
> 	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:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:722)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the infinispan-issues mailing list