RFR: 8230129: Add jtreg "serviceability/sa/ClhsdbInspect.java" to graal problem list.

[Xiaohong Gong (Arm Technology China)]

Hi dean,

  Sorry for my misunderstanding. I created a master bug JDK-8230419, and changed this issue as a Sub-Task for it.

Thanks,
Xiaohong Gong 

-----Original Message-----
From: Xiaohong Gong (Arm Technology China) 
Sent: Monday, September 2, 2019 10:04 AM
To: dean.long at oracle.com; hotspot-compiler-dev at openjdk.java.net; graal-dev at openjdk.java.net
Cc: nd <nd at arm.com>
Subject: RE: RFR: 8230129: Add jtreg "serviceability/sa/ClhsdbInspect.java" to graal problem list.

Hi dean,

  Currently there is not a master bug for this issue. A similar issue is JDK-8216181, but it is not entirely same. I'm not sure whether the root cause is the same one. So I will make this issue as the master bug and create another SubTask for it. Thanks.

Thanks,
Xiaohong Gong

-----Original Message-----
From: dean.long at oracle.com <dean.long at oracle.com>
Sent: Friday, August 30, 2019 7:40 AM
To: Xiaohong Gong (Arm Technology China) <Xiaohong.Gong at arm.com>; hotspot-compiler-dev at openjdk.java.net; graal-dev at openjdk.java.net
Cc: nd <nd at arm.com>
Subject: Re: RFR: 8230129: Add jtreg "serviceability/sa/ClhsdbInspect.java" to graal problem list.

Isn't it the correct process that there should be a master bug for fixing the test or underlying issue, then use that bug number for the problem list entry, and push it using a SubTask.  For example, see the relationship between JDK-8229447 and JDK-8229446 as an example.

dl

On 8/27/19 12:14 AM, Xiaohong Gong (Arm Technology China) wrote:
> Hi,
>
>    Please help to review this small patch:
>    Webrew: http://cr.openjdk.java.net/~pli/rfr/8230129/webrev.00/
>    JBS: https://bugs.openjdk.java.net/browse/JDK-8230129
>
>    Jtreg test "serviceability/sa/ClhsdbInspect.java" fails when 
> running with Graal. It fails when inspecting an address to check whether it's pointing to an expected oop or method, which is printed by running "jstack -v" firstly.
>    When running with graal, it needs more java heap for the JVMCI 
> initialization and the compiler working. So it's inevitable to make GC 
> happen during the application running. If GC happens after runnning "jstack", the actual address of the oops and methods may be different when running "inpsect". And the address inspected may point to other object or nothing.
>    A simple fix is to add this test to the graal problem list.
>
> Thanks,
> Xiaohong Gong