So the jtreg uncaughtException code is doing a join() on the target
Thread while holding the monitor lock of the ThreadGroup - ouch! Where
do we file jtreg bugs?
David
On 11/10/2011 1:44 AM, Chris Hegarty wrote:
On 10/10/2011 15:52, Alan Bateman wrote:
Chris Hegarty wrote:
Naoto,
Forgot to
Thanks, Chris. Will do it after confirming all's well with the JPRT
(currently it's down).
Naoto
On 10/10/11 7:27 AM, Chris Hegarty wrote:
Naoto,
Forgot to add, you can probably just push the changes for the test along
with your source changes. I modified it a little since last review.
Reprod
On 10/10/2011 15:52, Alan Bateman wrote:
Chris Hegarty wrote:
Naoto,
Forgot to add, you can probably just push the changes for the test
along with your source changes. I modified it a little since last
review. Reproduces one in about every ten times on one of our Dual
core Linux x64 boxes.
Is
Chris Hegarty wrote:
Naoto,
Forgot to add, you can probably just push the changes for the test
along with your source changes. I modified it a little since last
review. Reproduces one in about every ten times on one of our Dual
core Linux x64 boxes.
Is it the CME that duplicates for you? I'm
Naoto,
Forgot to add, you can probably just push the changes for the test along
with your source changes. I modified it a little since last review.
Reproduces one in about every ten times on one of our Dual core Linux
x64 boxes.
>: hg diff Bug6989440.java
diff -r 1e89a13d9d8f test/java/util
Thumbs up from me too.
-Chris.
On 10/10/2011 05:44, David Holmes wrote:
On 10/10/2011 1:35 PM, Naoto Sato wrote:
Hi David,
Thank you for your review. availableJRELocales is already declared with
volatile keyword in the current source, so no change is involved.
Sorry - my mistake. I misread
