geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-320) Snapshot tests failing due to a cache left by a previous test
Date Mon, 14 Sep 2015 20:55:46 GMT


ASF subversion and git services commented on GEODE-320:

Commit 4e65f0c72d30ca24c582543a62dc72b064e9d448 in incubator-geode's branch refs/heads/develop
from [~upthewaterspout]
[;h=4e65f0c ]

GEODE-320: Close the cache in DistributedTestCase tear down

Close the cache in distributed test case teardown to deal with bad
behaving tests that aren't cleaning up their cache.

Adding a log that shows us what tests ran previously to help debug
in situations where the progress file is not available.

I also found that RegionTestCase was previously not cleaning up the
cache at all, so I added a missing call to super.tearDown.

> Snapshot tests failing due to a cache left by a previous test
> -------------------------------------------------------------
>                 Key: GEODE-320
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>              Labels: CI
> Several of the snapshot tests failed in the last nightly build. It looks like a previous
test case left a cache running in some VMs. CacheTestCase would have cleaned this up, so it
looks like this may be caused by a previous test that doesn't extend CacheTestCase and doesn't
clean up after itself.
> {noformat} com.gemstone.gemfire.cache.snapshot.SnapshotByteArrayDUnitTest.testImportByteArray
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testCacheExportFilterException
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testExportAndImport
> com.gemstone.gemfire.cache.snapshot.SnapshotPerformanceDUnitTest.testPerformance
> {noformat}
> Sample failure:
> {noformat}
> java.lang.IllegalStateException: Cannot create region /PdxTypes DataPolicy withPersistence=true
because another cache (asf903(25185)<v618>:55958) has the same region DataPolicy withPersistence=false.
Persistent members must be started before non-persistent members
> 	at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.handleCacheDistributionAdvisee(
> 	at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.process(
> 	at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(
> 	at com.gemstone.gemfire.distributed.internal.DistributionMessage$
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(
> 	at com.gemstone.gemfire.distributed.internal.DistributionManager$5$
> 	at
> {noformat}

This message was sent by Atlassian JIRA

View raw message