JDK-8291054 : applications/javafuzzer/MediumTest.java fails "r2- 50" with 2 failures
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 20
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: aarch64
  • Submitted: 2022-07-26
  • Updated: 2022-07-27
  • Resolved: 2022-07-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 20
20Resolved
Related Reports
Duplicate :  
Relates :  
Description
The following test failed in the JDK20 CI:

applications/javafuzzer/MediumTest.java

Here's a snippet from the log file:

Summary of the JavaFuzzer run:
------------------------------
Host:     ol8-aarch64-690819
Tests:    8 x 50
Args:     -conf config.yml

Started  at: Tue Jul 26 16:40:51 UTC 2022


r1- 50: 34 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 16 Reference Java failures
r4- 50: 33 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 17 Reference Java failures
r3- 50: 30 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 20 Reference Java failures
r8- 50: 31 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 19 Reference Java failures
r5- 50: 34 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 16 Reference Java failures
r2- 50: 33 passed, 0 crashes, 2 fails, 0 hangs, 0 incorrect tests, 16 Reference Java failures
r6- 50: 30 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 20 Reference Java failures
r7- 50: 24 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 26 Reference Java failures

Finished at: Tue Jul 26 17:58:15 UTC 2022


[2022-07-26T17:58:15.361211790Z] Waiting for completion for process 247374
[2022-07-26T17:58:15.361369431Z] Waiting for completion finished for process 247374
----------System.err:(13/728)----------
java.lang.RuntimeException: assertEquals: expected 1 to equal 2
	at jdk.test.lib.Asserts.fail(Asserts.java:594)
	at jdk.test.lib.Asserts.assertEquals(Asserts.java:205)
	at jdk.test.lib.Asserts.assertEquals(Asserts.java:189)
	at applications.javafuzzer.JavaFuzzerRunner.main(JavaFuzzerRunner.java:235)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:578)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
	at java.base/java.lang.Thread.run(Thread.java:1589)

JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test

result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: assertEquals: expected 1 to equal 2

I downloaded the test run's artifacts and there are no hs_err_pid files. 
Taking a closer look at the above: 

r2- 50: 33 passed, 0 crashes, 2 fails, 0 hangs, 0 incorrect tests, 16 Reference Java failures

so we have "2 fails", but they didn't result in crashes.

I filed another recent failure for another fuzzer test:

JDK-8290910 applications/javafuzzer/BigTest.java fails "r6- 300" with 2 failures

and the synopsis has been updated to:

JDK-8290910 Incorrect result with C2 compiled code
Comments
Bisected to changeset for JDK-8283091.
27-07-2022

Reproduces with JDK 20 b3 but not JDK 20 b2.
26-07-2022

ILW = same as JDK-8290910 = P3
26-07-2022

Mismatch between "-XX:-TieredCompilation -XX:+IgnoreUnrecognizedVMOptions -XX:+UnlockDiagnosticVMOptions -XX:+StressLCM -XX:+StressGCM -XX:+StressIGVN -XX:+StressCCP -XX:StressSeed=1200687730 -Xmx1G -Xcomp -Xbatch" and "-Xmx1G -Xcomp -Xbatch" Possible duplicate of 8290910. I haven't bisected the problem to a specific changeset.
26-07-2022