@Test
  public void destroyWithEmptyRegionWithConcurrencyChecksCallsIndexManager() {
    givenConcurrencyChecks(true);
    givenRemoteEventWithVersionTag();
    givenIndexManager();

    doDestroy();

    verifyDestroyReturnedTrue();
    verifyIndexManagerOrder();
  }
This seems to be a bug. We should not leave an evictableEntry in the entryMap added by the
destroy call if destroy returns false.
geode-core/src/test/java/org/apache/geode/internal/cache/map/RegionMapDestroyTest.java