ben-manes / caffeine / #5116

100%

master: 100%

push

github

adjust discarding an in-flight refresh on entry creation

This can only happen if refreshIfNeeded was concurrent with the removal
so a dangling refresh was present. When the refresh completes it
validates the entry's write timestamp for ABA protection, which due to
nano time will certainly be different. Still, consistency is better for
fewer surprises and as a safetynet.

3813 of 3820 branches covered (99.82%)

2 of 2 new or added lines in 1 file covered. (100.0%)

7834 of 7834 relevant lines covered (100.0%)

1.0 hits per line