RFR(XS): 8252773: [TESTBUG] serviceability/jvmti/GetObjectSizeOverflow fails due to OOM conditions
Leonid Mesnik
leonid.mesnik at oracle.com
Thu Sep 3 20:37:33 UTC 2020
Hi
The exhausting of RAM could lead to unexpected failures of other tests
executed concurrently on this host and/or other environment related
issues. I think you might want to add *@requires* tag to skip test on
the hosts with small amount of RAM. Like '@requires os.maxMemory > 6G'.
See for detailed info:
https://openjdk.java.net/jtreg/tag-spec.html#requires_names
For real memory and cpu consumers we have separate directory
'resourcehogs/serviceability' where tests are not executed
non-concurrently. However these tests should be executed separately and
I think you need to move serviceability/jvmti/GetObjectSizeOverflow
there only you still see any problems after adding @requires tag.
Leonid
On 9/3/20 8:25 AM, Christoph Göttschkes wrote:
> Hi,
>
> please review the following patch for the GetObjectSizeOverflow test.
>
> Bug: https://bugs.openjdk.java.net/browse/JDK-8252773
> Webrev: https://cr.openjdk.java.net/~cgo/8252773/webrev.00
>
> The test case already handles out of memory conditions, but not if the
> whole JVM crashes because of it.
>
> Thanks,
> Christoph
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20200903/bb819319/attachment.htm>
More information about the serviceability-dev
mailing list