[infinispan-issues] [JBoss JIRA] (ISPN-2645) LocalKeyAffinityServiceTest.testFilteredRemoveServers fails randomly

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-2645:
--------------------------------

    Fix Version/s: 5.2.1

    
> LocalKeyAffinityServiceTest.testFilteredRemoveServers fails randomly
> --------------------------------------------------------------------
>
>                 Key: ISPN-2645
>                 URL: https://issues.jboss.org/browse/ISPN-2645
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache, Test Suite
>    Affects Versions: 5.2.0.Beta5
>            Reporter: Dan Berindei
>            Assignee: Mircea Markus
>              Labels: testsuite_stability
>             Fix For: 5.2.1, 5.3.0.Final
>
>
> LocalKeyAffinityServiceTest tests that KeyAffinnityServiceImpl's internal queues eventually fill up, and it fails:
> {noformat}
> java.lang.AssertionError: expected [true] but found [false]
> 	at org.testng.Assert.fail(Assert.java:89)
> 	at org.testng.Assert.failNotEquals(Assert.java:489)
> 	at org.testng.Assert.assertTrue(Assert.java:37)
> 	at org.testng.Assert.assertTrue(Assert.java:47)
> 	at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:76)
> 	at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:59)
> 	at org.infinispan.affinity.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:98)
> 	at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:108)
> 	at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:82)
> 	at org.infinispan.affinity.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:66)
> {noformat}
> I have added some TRACE logs to KeyAffinityServiceImpl and it looks like the queue fills up immediately, but it could be that a new queue is created and the test is checking the wrong queue object.

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