On 24/07/2013 12:21, David Holmes wrote:
On 24/07/2013 7:31 PM, Mandy Chung wrote:
On 7/24/2013 4:50 PM, shanliang wrote:
So we have 2 kinds of issues here:
1) the test related, like Thread state checking, we can fix them in
the test
2) MBean.getThreadCount() issue, we can create a bug to trac
On 24/07/2013 15:08, Jaroslav Bachorik wrote:
On 07/24/2013 03:17 PM, Chris Hegarty wrote:
On 24/07/2013 13:49, Jaroslav Bachorik wrote:
On 07/24/2013 02:32 PM, Chris Hegarty wrote:
On 24/07/2013 12:21, David Holmes wrote:
On 24/07/2013 7:31 PM, Mandy Chung wrote:
On 7/24/2013 4:50 PM, shan
On 24/07/2013 13:49, Jaroslav Bachorik wrote:
On 07/24/2013 02:32 PM, Chris Hegarty wrote:
On 24/07/2013 12:21, David Holmes wrote:
On 24/07/2013 7:31 PM, Mandy Chung wrote:
On 7/24/2013 4:50 PM, shanliang wrote:
So we have 2 kinds of issues here:
1) the test related, like Thread state check
On 07/25/2013 01:28 PM, Jaroslav Bachorik wrote:
..
I have filed a separate issue for hotspot/svc (JDK-8021335)
Yes, this is probably a separate, and more involved, issue.
For the time being I propose modifying the test to be less race-prone in
java and adding a timeout of 500ms after t
BTW - I wonder if you should add 8021335 in the @bug line.
-- daniel
On 7/25/13 2:37 PM, Daniel Fuchs wrote:
On 7/25/13 2:28 PM, Jaroslav Bachorik wrote:
For the time being I propose modifying the test to be less race-prone in
java and adding a timeout of 500ms after terminating a number of t
On 7/25/13 2:28 PM, Jaroslav Bachorik wrote:
For the time being I propose modifying the test to be less race-prone in
java and adding a timeout of 500ms after terminating a number of threads.
The test modifications are at
http://cr.openjdk.java.net/~jbachorik/8020875/webrev.02
Thanks,
Hi Jar
On 07/25/2013 07:07 AM, David Holmes wrote:
> On 25/07/2013 12:08 AM, Jaroslav Bachorik wrote:
>> On 07/24/2013 03:17 PM, Chris Hegarty wrote:
>>> On 24/07/2013 13:49, Jaroslav Bachorik wrote:
On 07/24/2013 02:32 PM, Chris Hegarty wrote:
> On 24/07/2013 12:21, David Holmes wrote:
>> On
