RFR: 8195600: [Graal] jdi tests timeouts with Graal because debuggee vm is not resumed
Chris Plummer
chris.plummer at oracle.com
Thu Aug 8 17:21:07 UTC 2019
Hi Daniil,
My only objection is at some point it seems we need to be able to run
these tests with graal (and other tests that have been disabled due to
graal) because graal might be the only compiler, and we'll lose test
coverage without these tests. Currently we have 260 jtreg tests disabled
due to graal. I'm not sure to what extent they are waiting on graal
fixes or otherwise have a bug filed to eventually fix them. Would be
nice if we had a process in place to make sure these issues are
eventually addressed. That fact that tests that exhaust memory in
general seem to be incompatible with graal would to be the bigger issue
that needs to be addressed.
thanks,
Chris
On 8/7/19 3:38 PM, Daniil Titov wrote:
> Please review the change that fixes the failing tests when running with Graal. The issue originally
> included several vmTestbase/nsk/jdi tests but only 2 of them still fail:
> - vmTestbase/nsk/jdi/VirtualMachine/instanceCounts/instancecounts003/instancecounts003.java
> - vmTestbase/nsk/jdi/ObjectReference/referringObjects/referringObjects002/referringObjects002.java
>
> The problem with these two tests is that they consume all memory to force the class unloading that
> results in the exception during JVMCI compiler initialization and the test failure.
>
> The fix filters these tests out to not run with Graal compiler.
>
> Webrev: http://cr.openjdk.java.net/~dtitov/8195600/webrev.01/
> Bug: https://bugs.openjdk.java.net/browse/JDK-8195600
>
> Thanks,
> Daniil
>
>
More information about the serviceability-dev
mailing list