[JBoss JIRA] (ISPN-5495) ConcurrentStartTest.testConcurrentStart random failures
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5495?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo commented on ISPN-5495:
-----------------------------------
what type if the first command received?
> ConcurrentStartTest.testConcurrentStart random failures
> -------------------------------------------------------
>
> Key: ISPN-5495
> URL: https://issues.jboss.org/browse/ISPN-5495
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 7.2.1.Final
> Reporter: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 8.2.0.CR1
>
>
> {noformat}
> org.testng.internal.thread.ThreadTimeoutException: Method org.testng.internal.TestNGMethod.testConcurrentStart() didn't finish within the time-out 60000
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)
> at org.infinispan.test.TestingUtil.waitForRehashToComplete(TestingUtil.java:253)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6236) StateTransferFunctionalTest random failures
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-6236?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-6236:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> StateTransferFunctionalTest random failures
> -------------------------------------------
>
> Key: ISPN-6236
> URL: https://issues.jboss.org/browse/ISPN-6236
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 8.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 8.2.0.CR1
>
>
> Since the ISPN-6214 fix, the global components are started when the {{DefaultCacheManager}} is started. This includes {{LocalTopologyManager}} and {{ClusterTopologyManager}}, created in the {{GlobalComponentRegistry}} constructor, and they also pull in the {{Transport}} component.
> In {{StateTransferFunctionalTest}} and its subclasses, this means the JGroups channel is created and joins the cluster before the {{JoiningNode}} registers its view listener. Because the listener is registered after the view update, it doesn't receive any notifications, and {{waitForJoin()}} always times out.
> We should remove the {{JoiningNode}} class altogether, because merges during initial cluster formation are practically impossible with our current test setup.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6236) StateTransferFunctionalTest random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6236?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6236:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4023
> StateTransferFunctionalTest random failures
> -------------------------------------------
>
> Key: ISPN-6236
> URL: https://issues.jboss.org/browse/ISPN-6236
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 8.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 8.2.0.CR1
>
>
> Since the ISPN-6214 fix, the global components are started when the {{DefaultCacheManager}} is started. This includes {{LocalTopologyManager}} and {{ClusterTopologyManager}}, created in the {{GlobalComponentRegistry}} constructor, and they also pull in the {{Transport}} component.
> In {{StateTransferFunctionalTest}} and its subclasses, this means the JGroups channel is created and joins the cluster before the {{JoiningNode}} registers its view listener. Because the listener is registered after the view update, it doesn't receive any notifications, and {{waitForJoin()}} always times out.
> We should remove the {{JoiningNode}} class altogether, because merges during initial cluster formation are practically impossible with our current test setup.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6236) StateTransferFunctionalTest random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6236?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6236:
-------------------------------
Summary: StateTransferFunctionalTest random failures (was: StateTrasnferFunctionalTest random failures)
> StateTransferFunctionalTest random failures
> -------------------------------------------
>
> Key: ISPN-6236
> URL: https://issues.jboss.org/browse/ISPN-6236
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 8.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 8.2.0.CR1
>
>
> Since the ISPN-6214 fix, the global components are started when the {{DefaultCacheManager}} is started. This includes {{LocalTopologyManager}} and {{ClusterTopologyManager}}, created in the {{GlobalComponentRegistry}} constructor, and they also pull in the {{Transport}} component.
> In {{StateTransferFunctionalTest}} and its subclasses, this means the JGroups channel is created and joins the cluster before the {{JoiningNode}} registers its view listener. Because the listener is registered after the view update, it doesn't receive any notifications, and {{waitForJoin()}} always times out.
> We should remove the {{JoiningNode}} class altogether, because merges during initial cluster formation are practically impossible with our current test setup.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month