RFR(XS) 8202359: [GRAAL] compiler/uncommontrap/TestDeoptOOM.java failed with OutOfMemoryError
vladimir.kozlov at oracle.com
Wed Oct 3 22:24:59 UTC 2018
Too late unfortunately - I pushed it.
I forgot about graal-specific problem list. We will need to do cleanup of !vm.graal.enabled anyway
when libgraal is introduced.
On 10/3/18 3:15 PM, Igor Ignatev wrote:
> It’d be better to put this test into the graal-specific problem list. This list has been introduced exactly for the cases like that, when we expect tests to become valid again as soon as we get libgraal. Marking it w/ !vm.graal.enabled means we don’t expect to work correctly w/ graal.
> — Igor
>> On Oct 3, 2018, at 2:48 PM, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
>>> On 10/3/18 2:46 PM, Igor Veresov wrote:
>>> Looks good.
>>>> On Oct 3, 2018, at 11:02 AM, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
>>>> Doug Simon wrote: This kind of test is always going to be a problem until we have libgraal. The test is intentionally consuming all available memory which means Graal will repeatedly fail with OOME during compilation.
>>>> I suggest to exclude this test from running with Java Graal:
>>>> diff -r 4236fa9582bb test/hotspot/jtreg/compiler/uncommontrap/TestDeoptOOM.java
>>>> --- a/test/hotspot/jtreg/compiler/uncommontrap/TestDeoptOOM.java
>>>> +++ b/test/hotspot/jtreg/compiler/uncommontrap/TestDeoptOOM.java
>>>> @@ -26,6 +26,7 @@
>>>> * @bug 6898462 8198826
>>>> * @summary failed reallocations of scalar replaced objects during deoptimization causes crash
>>>> + * @requires !vm.graal.enabled
>>>> * @run main/othervm -XX:-BackgroundCompilation -Xmx128M -XX:+IgnoreUnrecognizedVMOptions -XX:+VerifyStack
>>>> * -XX:CompileCommand=exclude,compiler.uncommontrap.TestDeoptOOM::main
>>>> * -XX:CompileCommand=exclude,compiler.uncommontrap.TestDeoptOOM::m9_1
More information about the hotspot-compiler-dev