ben-manes / caffeine

94%

master: 100%

LAST BUILD ON BRANCH v2.5.2

branch: v2.5.2

CHANGE BRANCH

x

Reset

• v2.5.2
• 05a040c2478341bab8a58a02b3dc1fe14d626d72
• 2.5.6
• Gil
• adaptive
• async-loader
• ben/issue30
• ben/spacing
• buffer
• cache2k
• clockpro
• codeql
• dependabot/github_actions/JetBrains/qodana-action-2023.1.4
• dependabot/github_actions/JetBrains/qodana-action-61b94e7e3a716dcb9e2030cfd79cd46149d56c26
• dependabot/github_actions/codecov/codecov-action-3.1.3
• dependabot/github_actions/github/codeql-action-2.3.4
• dependabot/gradle/com.gradle.common-custom-user-data-gradle-plugin-1.9
• dependabot/gradle/com.gradle.enterprise-3.14
• dependabot/gradle/de.thetaphi-forbiddenapis-3.6
• dependabot/gradle/pmd-7.0.0-rc4
• expiring_map
• expiry
• gil
• gilga
• gradient
• guava
• jctools
• juherr
• master
• memory
• orm
• penalties
• solr
• testng
• tmp
• travis
• v1.0
• v1.0.1
• v1.1.0
• v1.2.0
• v1.3.0
• v1.3.1
• v1.3.2
• v1.3.3
• v2.0.0
• v2.0.1
• v2.0.2
• v2.0.3
• v2.1.0
• v2.2.0
• v2.2.2
• v2.2.4
• v2.3.2
• v2.3.4
• v2.5.3
• v2.5.4
• v2.5.5
• v2.6.1
• v2.7.0
• v2.8.0
• v2.8.1
• v2.8.2
• v2.8.3
• v2.8.4
• v2.8.5
• v2.dev
• v3.0.5
• v3.0.6
• v3.1.0
• v3.1.1
• v3.1.2
• v3.1.4
• v3.1.5
• v3.1.6
• v3.1.7
• v3.1.8
• v3.dev

Build # 2072

Build Type

push

travis-ci

Committed by ben-manes

Commit Message

Fix variable expiration with async cache (fixes #159)

An in-flight future was mistakenly given the maximum expiry allowed,
causing it to not honor an expire-after-create setting. Instead it was
supposed to be beyond the maximum to signal adaption on the completion
update.

The calculations for fixed expiration was made more robust to the time
rolling over. This now complies with System.nanoTime() warnings.

Strengthened the remove and replace operations to be more predictably
linearizable. This removed optimizations to avoid unnecessary work by
checking if the entry was present in a lock-free manner. Since the hash
table supresses loads until complete, that might mean that a call to
remove a loading entry was not performed. The contract allows either,
so the optimization is left to user code and gives preference to those
who need the linearizable behavior. (See #156)

Run Details

5668 of 6032 relevant lines covered (93.97%)

0.94 hits per line