RFR (XS) 8220712: [TESTBUG] gc/shenandoah/compiler/TestMaybeNullUnsafeAccess should run with Shenandoah enabled

Aleksey Shipilev shade at redhat.com
Fri Mar 15 12:02:03 UTC 2019


Going to push this under triviality rules, okay?

-Aleksey

On 3/15/19 12:57 PM, Roman Kennke wrote:
> Yes. (Duh?)
> 
> Roman
> 
> 
>> Testbug:
>>    https://bugs.openjdk.java.net/browse/JDK-8220712
>>
>> Fix:
>>
>> diff -r 1def2d745747 -r 64c61d4df33c
>> test/hotspot/jtreg/gc/shenandoah/compiler/TestMaybeNullUnsafeAccess.java
>> --- a/test/hotspot/jtreg/gc/shenandoah/compiler/TestMaybeNullUnsafeAccess.java  Mon Mar 11 17:34:23
>> 2019 +0530
>> +++ b/test/hotspot/jtreg/gc/shenandoah/compiler/TestMaybeNullUnsafeAccess.java  Fri Mar 15 10:05:45
>> 2019 +0100
>> @@ -28,7 +28,12 @@
>>    * @requires vm.gc.Shenandoah
>>    * @modules java.base/jdk.internal.misc:+open
>>    *
>> - * @run main/othervm -XX:-UseOnStackReplacement -XX:-BackgroundCompilation -XX:-TieredCompilation
>> TestMaybeNullUnsafeAccess
>> + * @run main/othervm -XX:-UseOnStackReplacement -XX:-BackgroundCompilation -XX:-TieredCompilation
>> + *                   TestMaybeNullUnsafeAccess
>> + *
>> + * @run main/othervm -XX:-UseOnStackReplacement -XX:-BackgroundCompilation -XX:-TieredCompilation
>> + *                   -XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC
>> + *                   TestMaybeNullUnsafeAccess
>>    *
>>    */
>>
>> Testing: gc/shenandoah/compiler/ (includes the affected test) on Linux x86_64 {fastdebug|release}
>>
>> Thanks,
>> -Aleksey
>>




More information about the shenandoah-dev mailing list