@Test
  public void evictDestroyWithEmptyRegionDoesNothing() {
    givenConcurrencyChecks(false);
    givenEviction();

    doDestroy();

    verifyDestroyReturnedFalse();
    verify(regionMap, times(1)).getEntry(event);
    verifyNoMoreInteractions(regionMap);
    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