@Test
  public void destroyWhoseNewRegionEntryThrowsConcurrentCheckThrowsException() throws Exception {
    givenConcurrencyChecks(true);
    givenEventWithGatewayTag();
    givenEntryDestroyThrows(newRegionEntry, ConcurrentCacheModificationException.class);

    doDestroyExpectingThrowable();

    verifyThrowableInstanceOf(ConcurrentCacheModificationException.class);
    verify(owner, never()).notifyTimestampsToGateways(any());
    verifyNoDestroyInvocationsOnRegion();
  }
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