December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2615) org.infinispan.lock.StaleLocksTransactionTest testNoModsRollback and testNoModsCommit randomly fails

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2615: ----------------------------------- Summary: org.infinispan.lock.StaleLocksTransactionTest testNoModsRollback and testNoModsCommit randomly fails Key: ISPN-2615 URL: https://issues.jboss.org/browse/ISPN-2615 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.0.Beta5 Reporter: Anna Manukyan Assignee: Mircea Markus The tests are randomly failing on different environments. You can find the failures here: {code} Error Message expected [true] but found [false] Stacktrace 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.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:142) at org.infinispan.test.AbstractCacheTest.assertNotLocked(AbstractCacheTest.java:139) at org.infinispan.lock.StaleLocksTransactionTest.doTest(StaleLocksTransactionTest.java:79) at org.infinispan.lock.StaleLocksTransactionTest.testNoModsRollback(StaleLocksTransactionTest.java:61) 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: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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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) {code} {code} Error Message expected [true] but found [false] Stacktrace 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.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:142) at org.infinispan.test.AbstractCacheTest.assertNotLocked(AbstractCacheTest.java:139) at org.infinispan.lock.StaleLocksTransactionTest.doTest(StaleLocksTransactionTest.java:79) at org.infinispan.lock.StaleLocksTransactionTest.testNoModsRollback(StaleLocksTransactionTest.java:61) 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: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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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) {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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2599) The ping command in the CLI should be hidden

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2599?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2599: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The ping command in the CLI should be hidden > -------------------------------------------- > > Key: ISPN-2599 > URL: https://issues.jboss.org/browse/ISPN-2599 > Project: Infinispan > Issue Type: Feature Request > Components: CLI > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.2.0.Beta6 > > > ping is an internal command and should not appear -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2566) TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2566: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> made a comment on [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] Thanks Dan! I totally missed this fact. Will verify with ER6 then ;) > TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly > ------------------------------------------------------------------------------- > > Key: ISPN-2566 > URL: https://issues.jboss.org/browse/ISPN-2566 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.Beta4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.Beta6, 5.2.0.Final > > > Say we have a topology-aware cache with numOwners = 2 and two nodes: A(machine=m1) and B(machine=m1). When node C(machine=m2) joins, it should own every key, either as a primary or as a backup owner. This doesn't happen, node C owns just as many segments as nodes A and B. > Example: > {noformat} > 19:21:17,295 TRACE [org.infinispan.topology.ClusterTopologyManagerImpl] (undefined) Updating cache topology topology for rebalance: > CacheTopology{id=3, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1, > 32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 1 0, 68: 1 0, 69: 1 0, 70: 1 0, 71: 1 0, > 72: 1 0, 73: 1 0, 74: 1 0, 75: 1 0, 76: 1 0, 77: 1 0, 78: 1 0, 79: 1 0}, > pendingCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary), node2/default(secondary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 2 0, 28: 2 0, 29: 2 0, 30: 2 0, 31: 2 0, > 32: 2 0, 33: 2 0, 34: 2 0, 35: 2 0, 36: 2 0, 37: 2 0, 38: 2 0, 39: 2 0, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 2 1, 68: 2 1, 69: 2 1, 70: 2 1, 71: 2 1, > 72: 2 1, 73: 2 1, 74: 2 1, 75: 2 1, 76: 2 1, 77: 2 1, 78: 2 1, 79: 2 1}} > {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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2318) Reimplement a Topology-Aware Consistent Hash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2318?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2318: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> made a comment on [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] Thanks Dan! I totally missed this fact. Will verify with ER6 then ;) > Reimplement a Topology-Aware Consistent Hash > -------------------------------------------- > > Key: ISPN-2318 > URL: https://issues.jboss.org/browse/ISPN-2318 > Project: Infinispan > Issue Type: Task > Components: Core API, Distributed Cache > Affects Versions: 5.2.0.Alpha3 > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.Beta3 > > > Even with the advent of x-site replication, the TACH is useful to stripe key ownership across machines and/or racks for resiliency. This feature should be refactored from the 5.1 impl. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2318) Reimplement a Topology-Aware Consistent Hash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2318?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2318: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> made a comment on [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] Tomas, I don't think the fix is included in JDG ER5/Infinispan 5.2.0.Beta5. It will be included in ER6/Beta6. > Reimplement a Topology-Aware Consistent Hash > -------------------------------------------- > > Key: ISPN-2318 > URL: https://issues.jboss.org/browse/ISPN-2318 > Project: Infinispan > Issue Type: Task > Components: Core API, Distributed Cache > Affects Versions: 5.2.0.Alpha3 > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.Beta3 > > > Even with the advent of x-site replication, the TACH is useful to stripe key ownership across machines and/or racks for resiliency. This feature should be refactored from the 5.1 impl. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2566) TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2566: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> made a comment on [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] Tomas, I don't think the fix is included in JDG ER5/Infinispan 5.2.0.Beta5. It will be included in ER6/Beta6. > TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly > ------------------------------------------------------------------------------- > > Key: ISPN-2566 > URL: https://issues.jboss.org/browse/ISPN-2566 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.Beta4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.Beta6, 5.2.0.Final > > > Say we have a topology-aware cache with numOwners = 2 and two nodes: A(machine=m1) and B(machine=m1). When node C(machine=m2) joins, it should own every key, either as a primary or as a backup owner. This doesn't happen, node C owns just as many segments as nodes A and B. > Example: > {noformat} > 19:21:17,295 TRACE [org.infinispan.topology.ClusterTopologyManagerImpl] (undefined) Updating cache topology topology for rebalance: > CacheTopology{id=3, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1, > 32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 1 0, 68: 1 0, 69: 1 0, 70: 1 0, 71: 1 0, > 72: 1 0, 73: 1 0, 74: 1 0, 75: 1 0, 76: 1 0, 77: 1 0, 78: 1 0, 79: 1 0}, > pendingCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary), node2/default(secondary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 2 0, 28: 2 0, 29: 2 0, 30: 2 0, 31: 2 0, > 32: 2 0, 33: 2 0, 34: 2 0, 35: 2 0, 36: 2 0, 37: 2 0, 38: 2 0, 39: 2 0, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 2 1, 68: 2 1, 69: 2 1, 70: 2 1, 71: 2 1, > 72: 2 1, 73: 2 1, 74: 2 1, 75: 2 1, 76: 2 1, 77: 2 1, 78: 2 1, 79: 2 1}} > {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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2506) org.infinispan.config.parsing.JdbcConfigurationTest.testParseCacheLoaders fails periodically

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2506?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2506: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 872238|https://bugzilla.redhat.com/show_bug.cgi?id=872238] The failure doesn't appear any more. Thanks, verified! > org.infinispan.config.parsing.JdbcConfigurationTest.testParseCacheLoaders fails periodically > -------------------------------------------------------------------------------------------- > > Key: ISPN-2506 > URL: https://issues.jboss.org/browse/ISPN-2506 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Tristan Tarrant > Labels: testsuite_stability > Fix For: 5.2.0.Beta5, 5.2.0.Final > > > The test failures are: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2506) org.infinispan.config.parsing.JdbcConfigurationTest.testParseCacheLoaders fails periodically

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2506?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2506: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 872238|https://bugzilla.redhat.com/show_bug.cgi?id=872238] from ON_QA to VERIFIED > org.infinispan.config.parsing.JdbcConfigurationTest.testParseCacheLoaders fails periodically > -------------------------------------------------------------------------------------------- > > Key: ISPN-2506 > URL: https://issues.jboss.org/browse/ISPN-2506 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Tristan Tarrant > Labels: testsuite_stability > Fix For: 5.2.0.Beta5, 5.2.0.Final > > > The test failures are: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2176) Test LocalKeyAffinityServiceTest.testFilteredSingleKey fail randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2176?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2176: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 843785|https://bugzilla.redhat.com/show_bug.cgi?id=843785] from ON_QA to VERIFIED > Test LocalKeyAffinityServiceTest.testFilteredSingleKey fail randomly > -------------------------------------------------------------------- > > Key: ISPN-2176 > URL: https://issues.jboss.org/browse/ISPN-2176 > Project: Infinispan > Issue Type: Task > Affects Versions: 5.1.6.FINAL > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Minor > Labels: jdg, jdg6, testsuite_stability > Fix For: 5.2.0.Beta3 > > Attachments: failed_test.txt > > > Example failure can be found at https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/ed... > In the next run everything was fine: > https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/ed... -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2176) Test LocalKeyAffinityServiceTest.testFilteredSingleKey fail randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2176?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2176: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 843785|https://bugzilla.redhat.com/show_bug.cgi?id=843785] The failure does not appear any more. > Test LocalKeyAffinityServiceTest.testFilteredSingleKey fail randomly > -------------------------------------------------------------------- > > Key: ISPN-2176 > URL: https://issues.jboss.org/browse/ISPN-2176 > Project: Infinispan > Issue Type: Task > Affects Versions: 5.1.6.FINAL > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Minor > Labels: jdg, jdg6, testsuite_stability > Fix For: 5.2.0.Beta3 > > Attachments: failed_test.txt > > > Example failure can be found at https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/ed... > In the next run everything was fine: > https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/ed... -- 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

12 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012