FW: is this a bug ?

[Yangfei (Felix)]

> On 10/16/19 10:45 AM, Aleksey Shipilev wrote:
> >> Patch is trivial:
> >> diff -r 7dce6af27fd5
> tests-custom/src/main/java/org/openjdk/jcstress/tests/atomicity/buffers/Dire
> ctByteBufferViewsAtomicityTests.java
> >> ---
> a/tests-custom/src/main/java/org/openjdk/jcstress/tests/atomicity/buffers/Di
> rectByteBufferViewsAtomicityTests.java  Sun Aug 11 10:37:40 2019 +0200
> >> +++
> b/tests-custom/src/main/java/org/openjdk/jcstress/tests/atomicity/buffers/Di
> rectByteBufferViewsAtomicityTests.java  Thu Aug 15 14:42:49 2019 +0800
> >> @@ -52,7 +52,7 @@
> >>          private final ShortBuffer sb;
> >>
> >>          public MyState() {
> >> -            b = ByteBuffer.allocate(16);
> >> +            b = ByteBuffer.allocateDirect(16);
> >>              b.order(ByteOrder.nativeOrder());
> >>              ib = b.asIntBuffer();
> >>              cb = b.asCharBuffer();
> 
> I mean, yes, that is a test bug:
>   http://hg.openjdk.java.net/code-tools/jcstress/rev/4d196b66fcb1
> 
> But have you actually see it fail? I don't see how, as test grading accepts all
> results.

Yes, it fails randomly on our 128-core aarch64 server platform.  

Part of the report was:

ERROR tests
Tests break for some reason, other than failing the assert. Correct implementations should have none.

   o.o.j.t.atomicity.buffers.DirectByteBufferViewsAtomicityTests.LongViewTest

Exception in thread "main" java.lang.IllegalStateException: Should have been handled within the Runner
	at org.openjdk.jcstress.JCStress.runEmbedded(JCStress.java:248)
	at org.openjdk.jcstress.ForkedMain.main(ForkedMain.java:55)
JVM options: [-XX:+UnlockDiagnosticVMOptions, -XX:+WhiteBoxAPI, -XX:-RestrictContended, -XX:-TieredCompilation, -XX:ReservedCodeCacheSize=128M, -server] Iterations: 5 Time: 1000