[infinispan-issues] [JBoss JIRA] (ISPN-2720) StateTransferPessimisticTest.testStateTransfer fails randomly

Adrian Nistor (JIRA) jira-events at lists.jboss.org
Fri Feb 1 10:30:51 EST 2013


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

Adrian Nistor commented on ISPN-2720:
-------------------------------------

The test counts the owners of the key after state transfer by looking directly into the data container and finds too many because expiration was not taken into account.
                
> StateTransferPessimisticTest.testStateTransfer fails randomly
> -------------------------------------------------------------
>
>                 Key: ISPN-2720
>                 URL: https://issues.jboss.org/browse/ISPN-2720
>             Project: Infinispan
>          Issue Type: Bug
>          Components: State transfer
>    Affects Versions: 5.2.0.CR1
>            Reporter: Galder Zamarreño
>            Assignee: Adrian Nistor
>              Labels: testsuite_stability
>             Fix For: 5.2.1, 5.3.0.Alpha1
>
>         Attachments: testStateTransfer-6.tgz
>
>
> {code}testStateTransfer(org.infinispan.statetransfer.StateTransferPessimisticTest)  Time elapsed: 0.174 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<2>
> 	at org.junit.Assert.fail(Assert.java:93)
> 	at org.junit.Assert.failNotEquals(Assert.java:647)
> 	at org.junit.Assert.assertEquals(Assert.java:128)
> 	at org.junit.Assert.assertEquals(Assert.java:472)
> 	at org.junit.Assert.assertEquals(Assert.java:456)
> 	at org.infinispan.statetransfer.StateTransferPessimisticTest.testStateTransfer(StateTransferPessimisticTest.java:104)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:767)
> 	at org.testng.TestRunner.run(TestRunner.java:617)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> 	at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> 	at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:680){code}

--
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