Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upComments
added a commit
to timeck/jsr107tck
that referenced
this issue
Nov 22, 2014
added a commit
to timeck/jsr107tck
that referenced
this issue
Nov 22, 2014
gregrluck
added
the
TCK Challenge
label
Dec 12, 2014
gregrluck
added this to the 1.1.0 milestone
Dec 12, 2014
This comment has been minimized.
This comment has been minimized.
|
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. |
gregrluck
modified the milestones:
1.0.1,
1.1.0
Jul 23, 2015
This comment has been minimized.
This comment has been minimized.
|
Moving this to 1.0.1. Implementations will have to fix their behaviour. |
gregrluck
closed this
in
c217f1d
Jul 23, 2015
cruftex
referenced this issue
Sep 20, 2015
Closed
Relax JMX Statistics Testing in accordance with the Specification #79
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
timeck commentedNov 22, 2014
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 statistics