[JBoss JIRA] (ISPN-4194) VersionedDistStateTransferTest.testStateTransfer random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4194?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4194:
-------------------------------
Summary: VersionedDistStateTransferTest.testStateTransfer random failures (was: VersionedDistStateTransferTesttestStateTransfer random failures)
> VersionedDistStateTransferTest.testStateTransfer random failures
> ----------------------------------------------------------------
>
> Key: ISPN-4194
> URL: https://issues.jboss.org/browse/ISPN-4194
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 7.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 7.0.0.Alpha3
>
>
> The test was using {{MultipleCacheManagersTest.waitForClusterToForm()}} after killing a member, but sometimes we get this exception because one of the member hasn't updated its view right away:
> {noformat}
> 16:38:13,013 ERROR (testng-VersionedDistStateTransferTest:) [UnitTestTestNGListener] Test testStateTransfer(org.infinispan.container.versioning.VersionedDistStateTransferTest) failed.java.lang.IllegalStateException: Cache
> at address NodeE-23064 had 5 members; expecting 4. Members were (NodeA-26412, NodeB-21974, NodeC-26057, NodeD-43882, NodeE-23064)
> at org.infinispan.test.TestingUtil.isCacheViewComplete(TestingUtil.java:461)
> at org.infinispan.test.TestingUtil.areCacheViewsComplete(TestingUtil.java:409)
> at org.infinispan.test.TestingUtil.areCacheViewsComplete(TestingUtil.java:401)
> at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:238)
> at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:284)
> at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:911)
> at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:226)
> at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:233)
> at org.infinispan.container.versioning.VersionedDistStateTransferTest.testStateTransfer(VersionedDistStateTransferTest.java:96)
> {noformat}
> The solution is to use just {{TestingUtil.waitForRehashToComplete()}} when killing a node.
--
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
[JBoss JIRA] (ISPN-4194) VersionedDistStateTransferTesttestStateTransfer random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4194:
----------------------------------
Summary: VersionedDistStateTransferTesttestStateTransfer random failures
Key: ISPN-4194
URL: https://issues.jboss.org/browse/ISPN-4194
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Affects Versions: 7.0.0.Alpha2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.0.0.Alpha3
The test was using {{MultipleCacheManagersTest.waitForClusterToForm()}} after killing a member, but sometimes we get this exception because one of the member hasn't updated its view right away:
{noformat}
16:38:13,013 ERROR (testng-VersionedDistStateTransferTest:) [UnitTestTestNGListener] Test testStateTransfer(org.infinispan.container.versioning.VersionedDistStateTransferTest) failed.java.lang.IllegalStateException: Cache
at address NodeE-23064 had 5 members; expecting 4. Members were (NodeA-26412, NodeB-21974, NodeC-26057, NodeD-43882, NodeE-23064)
at org.infinispan.test.TestingUtil.isCacheViewComplete(TestingUtil.java:461)
at org.infinispan.test.TestingUtil.areCacheViewsComplete(TestingUtil.java:409)
at org.infinispan.test.TestingUtil.areCacheViewsComplete(TestingUtil.java:401)
at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:238)
at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:284)
at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:911)
at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:226)
at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:233)
at org.infinispan.container.versioning.VersionedDistStateTransferTest.testStateTransfer(VersionedDistStateTransferTest.java:96)
{noformat}
The solution is to use just {{TestingUtil.waitForRehashToComplete()}} when killing a node.
--
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
[JBoss JIRA] (ISPN-3904) Migrate JDBC cache store tests
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3904?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3904:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Alpha3
Resolution: Done
> Migrate JDBC cache store tests
> ------------------------------
>
> Key: ISPN-3904
> URL: https://issues.jboss.org/browse/ISPN-3904
> Project: Infinispan
> Issue Type: Task
> Components: Server
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: task
> Fix For: 7.0.0.Alpha3
>
>
> Migrating finctional tests for JDBC cache store
> Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
> There is issue with passivating oldest entries https://issues.jboss.org/browse/ISPN-4187 . Should be resolved
--
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
[JBoss JIRA] (ISPN-3904) Migrate JDBC cache store tests
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-3904?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-3904:
------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/2398 (was: https://github.com/infinispan/infinispan/pull/2339, https://github.com/infinispan/infinispan/pull/2398)
> Migrate JDBC cache store tests
> ------------------------------
>
> Key: ISPN-3904
> URL: https://issues.jboss.org/browse/ISPN-3904
> Project: Infinispan
> Issue Type: Task
> Components: Server
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: task
>
> Migrating finctional tests for JDBC cache store
> Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
> There is issue with passivating oldest entries https://issues.jboss.org/browse/ISPN-4187 . Should be resolved
--
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
[JBoss JIRA] (ISPN-3904) Migrate JDBC cache store tests
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-3904?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-3904:
------------------------------------
Description:
Migrating finctional tests for JDBC cache store
Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
There is issue with passivating oldest entries https://issues.jboss.org/browse/ISPN-4187 . Should be resolved
was:
Migrating finctional tests for JDBC cache store
Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
> Migrate JDBC cache store tests
> ------------------------------
>
> Key: ISPN-3904
> URL: https://issues.jboss.org/browse/ISPN-3904
> Project: Infinispan
> Issue Type: Task
> Components: Server
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: task
>
> Migrating finctional tests for JDBC cache store
> Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
> There is issue with passivating oldest entries https://issues.jboss.org/browse/ISPN-4187 . Should be resolved
--
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
[JBoss JIRA] (ISPN-3904) Migrate JDBC cache store tests
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3904?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3904:
-----------------------------------
Status: Pull Request Sent (was: Pull Request Sent)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2339, https://github.com/infinispan/infinispan/pull/2398 (was: https://github.com/infinispan/infinispan/pull/2339)
> Migrate JDBC cache store tests
> ------------------------------
>
> Key: ISPN-3904
> URL: https://issues.jboss.org/browse/ISPN-3904
> Project: Infinispan
> Issue Type: Task
> Components: Server
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: task
>
> Migrating finctional tests for JDBC cache store
> Following modules will be migrated: async-store, binary-no-passivation, binary-with-passivation, invalidation-cache, mixed-no-passivation, mixed-with-passivation, string-based-multinode, string-based-no-passivation, string-based-with-passivation
--
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