Roger,
Jon is correct, we had several options for test stabilization, including
fixing several dozen tests that were written a decade before -agentvm
came into being. See the bug and this external link for more details:
http://mail.openjdk.java.net/pipermail/security-dev/2013-November/009701.html
We could certainly request such a switch and "clean" those tests, but
with this new JPRT switch for -agentvm, it no longer seems necessary
esp. given limited cycles.
Brad
On 12/3/2013 8:44 AM, Jonathan Gibbons wrote:
Roger,
That conflicts with the wishes of the security team who requested that
jtreg clean up the security providers -- i.e. they don't want their
tests to have to worry about it. The security team filed the request
for 7900248.
So, I think you and the security team need to figure out the coding
style and pattern you want and then figure out what jtreg support you need.
-- Jon
On 12/03/2013 06:47 AM, roger riggs wrote:
Hi Jon,
I'd like to see a log message flagging a test that does not
restore the log providers. Otherwise, we're going to encourage
poor hygiene in tests and won't know the extent of the use/misuse.
Roger
On 12/2/2013 9:09 PM, [email protected] wrote:
Changeset: 8218bff65772
Author: jjg
Date: 2013-12-02 18:07 -0800
URL: http://hg.openjdk.java.net/code-tools/jtreg/rev/8218bff65772
7900248: Enhance jtreg to copy/restore the Security Providers when
running in agentvm or samevm mode.
+ make/tests/SecurityProviderTest.gmk
! src/share/classes/com/sun/javatest/regtest/Action.java
+ src/share/test/javatest/regtest/data/secprov/A.java
+ src/share/test/javatest/regtest/data/secprov/B.java
+ src/share/test/javatest/regtest/data/secprov/C.java
+ src/share/test/javatest/regtest/data/secprov/TEST.ROOT
+ src/share/test/javatest/regtest/data/secprov/Test.java
