RFR: 8249543: Force DirectBufferAllocTest to run with -ExplicitGCInvokesConcurrent

[Alan Bateman]

On 15/07/2020 18:20, rkennke at redhat.com wrote:
> DirectBufferAllocTest is unreliable when running with
> +ExplicitGCInvokesConcurrent, because allocating DBB spreads
> System.gc() calls all over concurrent GC cycles. It becomes more
> reliable when running with -ExplicitGCInvokesConcurrent. (Shenandoah
> defaults to +ExplicitGCInvokesConcurrent, other GCs don't as far as I
> know.)
>
> Bug:
> https://bugs.openjdk.java.net/browse/JDK-8249543
> Webrev:
> http://cr.openjdk.java.net/~rkennke/JDK-8249543/webrev.00/
>
> Ok?
>
I guess this is okay but if -ExplicitGCInvokesConcurrent is the default 
then doesn't it break RMI DGC?  Are you sure this is the only test that 
fails?

-Alan