Spring/spring-data-gemfire
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SGF-320 - Disable ClusterConfigurationIntegrationTest.testClusterConfiguration test case.

Browse Source 
Due to a race condition/bug in the new GemFire 8 Locator Cluster Configuration Service on startup, the race is causing a timing issue for the testClusterConfiguration test case in the CI (Bamboo) env even though the test case runs successfully, locally.  These timing issues are despite an appropriate and reasonable wait period setup by the test class where the 'integration-based' test is attempting to coordinate between a forked GemFire Locator process hosting the Cluster Config Service and the test case, which is a peer cache, that uses it.
This commit is contained in:
John Blum
2014-09-04 12:58:11 -07:00
parent fe53d07923
commit 458b1ff25e
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/test/java/org/springframework/data/gemfire/CacheClusterConfigurationIntegrationTest.java
View File

@@ -30,6 +30,7 @@ import java.util.concurrent.TimeUnit;
import org.junit.AfterClass;
import org.junit.BeforeClass;
import org.junit.Ignore;
import org.junit.Rule;
import org.junit.Test;
import org.junit.rules.TestRule;
@@ -202,6 +203,8 @@ public class CacheClusterConfigurationIntegrationTest {
}
@Test
@Ignore
// TODO re-enable the test once the GemFire Cluster Configuration Service race condition has been properly fixed!
public void testClusterConfiguration() {
ConfigurableApplicationContext applicationContext = newApplicationContext(
getLocation("cacheUsingClusterConfigurationIntegrationTest.xml"));