@Test
  public void destroyWithEmptyRegionWithConcurrencyChecksAndEventWithConflictAddsATombstone()
      throws Exception {
    givenConcurrencyChecks(true);
    givenRemoteEventWithVersionTag();
    givenEventWithConflict();

    doDestroy();

    verifyDestroyReturnedTrue();
    verifyEntryAddedToMap(newRegionEntry);
    verifyEntryDestroyed(newRegionEntry, true);
    verifyInvokedDestroyMethodsOnRegion(false);
  }
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