Hi Alan
How did you notice the problem?
Webrev at
http://cr.openjdk.java.net/~weijun/7094842/webrev.00
Here I change the threads to non-daemon, so that if there is anything
wrong, there will be a timeout (which sounds better than bringing all
tests slow).
Although Synch2 is in othervm mode, I change the style also.
*Jon*: shouldn't jtreg kill the daemon threads?
I've submitted a testonly JPRT job on jdk_security3 for this.
Thanks
Max
On 09/26/2011 03:00 AM, [email protected] wrote:
*Change Request ID*: 7094842
*Synopsis*:
test/javax/security/auth/Subject/{Synch.java,Synch2.java,Synch3.java} loop
forever in agentvm mode
Product: java
Category: jaas
Subcategory: auth
=== *Description* ============================================================
The following tests are unsuited for running in samevm or agentvm mode:
test/javax/security/auth/Subject/Synch.java,
test/javax/security/auth/Subject/Synch2.java
test/javax/security/auth/Subject/Synch3.java
Each of the tests starts a thread that spins forever and this causes all
subsequent tests to run very slowly or timeout.
These tests need to be fixed quickly so that they run in othervm mode.
Alternatively a better solution is for the thread to terminate when the test
completes.
