geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <>
Subject [jira] [Commented] (GEODE-218) Change distributedTest task to fork every 1 test case
Date Fri, 04 Sep 2015 18:03:45 GMT


Kirk Lund commented on GEODE-218:

On my CentOS 6.5 machine, this change increases the build time from 6 hr 16 min to 9 hr 38
min. The following dunit tests failed despite having fresh JVMs:

* com.gemstone.gemfire.cache.query.dunit.QueryUsingFunctionContextDUnitTest.testQueriesWithFilterKeysOnPRWithRebalancing
* com.gemstone.gemfire.cache.query.partitioned.PRQueryRegionDestroyedDUnitTest.testPRWithRegionDestroyInOneDatastoreWithDelay
* com.gemstone.gemfire.internal.cache.tier.sockets.Bug37210DUnitTest.testHAStatsCleanup

> Change distributedTest task to fork every 1 test case
> -----------------------------------------------------
>                 Key: GEODE-218
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
> Change distributedTest task in the root build.gradle from "forkEvery 30" to "forkEvery
> DUnit tests are continuing to have spurious failures. Two common causes are: 1) stop-the-world
GC pauses, 2) JVM pollution from a previous test.
> The best overall way to reduce the number of spurious failures and hopefully get our
automated tests running green again is to isolate each test case more thoroughly by having
each DUnit fork new JVMs. We can reevaluate this after seeing what effect "forkEvery 1" has.
> For purposes of execution speed, we should try to prevent the test (UnitTests) and integrationTest
(IntegrationTests) tasks from forking. It's also more important to have distributedTest (DIstributedTests)
fork because these are end-to-end tests using a cluster of 6 JVMs.

This message was sent by Atlassian JIRA

View raw message