RFR(T) 8230110: TestLinkageErrorInGenerateOopMap times out

[Tobias Hartmann]

Hi Arno,

looks good to me too.

Best regards,
Tobias

On 25.09.19 11:10, Langer, Christoph wrote:
> Hi Arno,
> 
> this testfix seems reasonable, +1.
> 
> You’ve posted it to the wrong mailing list, though. It should be directed to hotspot-compiler-dev, hence I’ve copied this list in my reply. Bcc-ing compiler-dev.
> 
> Best regards
> Christoph
> 
> From: compiler-dev <compiler-dev-bounces at openjdk.java.net> On Behalf Of Thomas Stüfe
> Sent: Mittwoch, 25. September 2019 08:05
> To: Zeller, Arno <arno.zeller at sap.com>
> Cc: compiler-dev at openjdk.java.net
> Subject: Re: RFR(T) 8230110: TestLinkageErrorInGenerateOopMap times out
> 
> Hi Arno,
> 
> Seems reasonable, assuming you verified that 64m heap are enough for this test on all platforms.
> 
> I can sponsor this for you.
> 
> Cheers, Thomas
> 
> On Wed, Sep 25, 2019, 07:57 Zeller, Arno <arno.zeller at sap.com<mailto:arno.zeller at sap.com>> wrote:
> Hi,
> 
> I have seen some occurrences of this issue (8230110) on our AIX and Windows test machines. The test times out because it writes a huge core file (I have seen more than 24GB on one machine) and this might take minutes.
> As far as I understand the test does not need a core file. Therefore my suggestion is to set a max java heap size (-Xmx64m) and switch of core file writing (-XX:-CreateCoredumpOnCrash).
> 
> Reopened bug: https://bugs.openjdk.java.net/browse/JDK-8230110
> Webrev: http://cr.openjdk.java.net/~azeller/webrevs/JKD8230110_TestLinkageErrorInGenerateOopMap_times_out/webrev/
> 
> I am no committer – I will need a sponsor for this change.
> 
> Best regards,
> Arno
>