RFR(XXS): 8213707: [TEST] vmTestbase/nsk/stress/except/except011.java failed due to wrong class name
zgu at redhat.com
Sat Nov 10 01:59:12 UTC 2018
Thanks for reviewing, David.
On 11/9/18 5:58 PM, David Holmes wrote:
> Looks good - thanks for finding and fixing.
> I see cases internally where we fail because of this:
> Failure: ExceptionInInitializerError: target class not found
> but no bug was ever filed. I wonder if we will now fail because of the
> OOME ...
Actually, it has to avoid OOME to get to here.
Several nsk/stress/except tests, e.g. except001, except002 and etc.
depend on quick OOME to pass.
Shenandoah has mechanism to gradually slow down allocation, so it is
more resist to OOME. Unfortunately, it usually fails due to timeout.
I am wondering of the usefulness of these tests.
> On 10/11/2018 7:43 AM, Zhengyu Gu wrote:
>> Please review this trivial fix.
>> Currently, only Shenandoah experiences the failure, since other GCs
>> run out Java heap memory, then the rest of test is skipped.
>> pool=new Object(); // elapsed 10.287s
>> pool=new Object(); // elapsed 7.947s
>> Heap seems exhausted - OutOfMemoryError thrown.
>> Skipped: ExceptionInInitializerError: thrown OutOfMemoryError
>> Test passed.
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8213707
>> Webrev: http://cr.openjdk.java.net/~zgu/8213707/webrev.00/
More information about the hotspot-dev