org.jsr107.tck.management.CacheMBStatisticsBeanTest.testPutIfAbsent() #63
Labels
Milestone
Comments
timeck
added a commit
to timeck/jsr107tck
that referenced
this issue
Nov 22, 2014
timeck
added a commit
to timeck/jsr107tck
that referenced
this issue
Nov 22, 2014
Yes you are correct. This change will break all of the existing implementations who have all followed the incorrect test and the incorrect RI. We are therefore setting this 1.1.0 of the TCK which under the rules is not mandatory for 1.0 implementations. See the TCK Users Guide. |
Moving this to 1.0.1. Implementations will have to fix their behaviour. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test asserts that neither the "hit" or "miss" counts are affected by two
Cache.putIfAbsent()
operationsThe spec lists this however (page 131):
I am of the opinion that the first
putIfAbsent()
would count as both a "put" and a "miss", and the second call would record a "hit" in the cache statisticsThe text was updated successfully, but these errors were encountered: