On 1/17/2014 6:51 AM, Daniel Fuchs wrote:
Hi,
Please find below a webrev for:
8031980: Add new j.u.l deadlock test for JDK-8027670 and JDK-8029281
https://bugs.openjdk.java.net/browse/JDK-8031980
<http://cr.openjdk.java.net/~dfuchs/webrev_8031980/webrev.00/>
The new test looks reasonable. "foo.bar5.level = INFO" is commented
out in deadlock.conf.properties. Is this intentional? The test runs in
the same VM first without security manager and then with security
manager. The loggers have been created and may/may not be GC'ed. I
wonder if it's worth breaking them into two separate runs so that each
run starts with no logger. Have you also tried running this with
-Xcomp and see if any intermittent failure due to GC? It looks fine
when reviewing the test but better to verify it.
Mandy