On 02/16/2015 06:32 PM, Anthony Scarpino wrote:
On 02/16/2015 02:48 PM, Sean Mullan wrote:
On 02/16/2015 02:57 PM, Anthony Scarpino wrote:
FYI, the bug number should be JDK-8043951. The one I listed was the
backport ID. The link below is still valid
Normally, the bug in the comment above a problem list entry is the bug
that remains open and still needs to be fixed for the problem entry to
be removed, and you open a separate bug to add the entry to the problem
list. So you should open a new bug (ex: add
sun/security/pkcs11/MessageDigest/TestCloning.java to ProblemList) and
leave 8043951 open.
--Sean
I understand what you're saying, but I'm not sure how keeping 8043951
open will help given this is an infrastructure issue. Once disabled, we
will never know really when it's fixed from a product standpoint.
Ok, what you are basically saying is that this ProblemList entry should
never be removed. That is probably not a good usage of ProblemList.
If we want the bug in the ProblemList to remain open, I would say
putting the infrastructure bug number INTJDK-7613285 would be best.
That bug is non-public though (Oracle-specific).
Maybe it makes more sense to change the test to check if the os.name is
Solaris and the os.version is < 11, and not continue instead of adding a
ProblemList entry.
--Sean
Tony
On 02/16/2015 11:51 AM, Anthony Scarpino wrote:
I'd like a review for adding this TestCloning.java to the ProblemList.
This change is not because of a functional problem in Java, it's
because
testing continues to occur on unpatched Solaris 10 machines for this
Solaris bug. The test will continue to run on Solaris 11, where the
problem doesn't exist so we are not missing test coverage.
Additionally,
this is only going to JDK8u because Solaris 10 is not supported in
JDK9.
http://cr.openjdk.java.net/~ascarpino/8073113-8u/webrev/
Tony
