JDK-8316692 : applications/javafuzzer/BigTest.java failed with "assertEquals: expected 1 to equal 2"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 22
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86_64
  • Submitted: 2023-09-21
  • Updated: 2024-06-25
  • Resolved: 2023-09-22
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 22
22Resolved
Related Reports
Duplicate :  
JDK-8316396 - Endless loop in C2 compilation triggered by AddNode::IdealIL
Relates :  
JDK-8335125 - Test applications/javafuzzer/BigTest.java failed with "assertEquals: expected 1 to equal 2"
Description
The following test failed in the JDK22 CI:

applications/javafuzzer/BigTest.java

Here's a snippet from the log file:

#section:driver
----------messages:(7/309)----------
command: driver applications.javafuzzer.JavaFuzzerRunner -NT 300
reason: User specified action: run driver/timeout=100000 applications.javafuzzer.JavaFuzzerRunner -NT 300 
started: Thu Sep 21 07:42:17 UTC 2023
Mode: agentvm
Agent id: 2
finished: Thu Sep 21 17:24:11 UTC 2023
elapsed time (seconds): 34914.283
----------configuration:(16/2434)----------

<snip>

----------System.out:(36/2683)----------
For random generator using seed: -7849352783869804813
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=-7849352783869804813" to command line.
Using JRuby executable: /opt/mach5/mesos/work_dir/jib-master/install/org/jruby/jruby-dist/9.2.12.0/jruby-dist-9.2.12.0-bin.zip/jruby-9.2.12.0/bin/jruby
Starting JavaFuzzer: '/bin/bash /opt/mach5/mesos/work_dir/jib-master/install/com/oracle/jpg/bigapps/javafuzzer/javafuzzer/2.0/javafuzzer-2.0.zip/mrt.sh -R /opt/mach5/mesos/work_dir/slaves/cd627e65-f015-4fb1-a1d2-b6c9b8127f98-S182651/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/15762a09-5e76-4f46-95e7-8ec723663054/runs/2bb67277-e695-41fc-acff-45ca7835b25f/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_javafuzzer_BigTest_java/scratch/0 -NT 300 -NP 12 -A -conf config.yml'
[2023-09-21T07:42:23.176030584Z] Gathering output for process 15490
[2023-09-21T17:24:11.206727647Z] Waiting for completion for process 15490
[2023-09-21T17:24:11.207025080Z] Waiting for completion finished for process 15490
Output and diagnostic info for process 15490 was saved into 'pid-15490-output.log'

Summary of the JavaFuzzer run:
------------------------------
Host:     ol7-x64
Tests:    12 x 300
Args:     -conf config.yml

Started  at: Thu Sep 21 07:42:23 UTC 2023


r3- 300: 186 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 114 Reference Java failures
r7- 300: 195 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 105 Reference Java failures
r9- 300: 193 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 107 Reference Java failures
r5- 300: 173 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 127 Reference Java failures
r12- 300: 170 passed, 0 crashes, 2 fails, 0 hangs, 0 incorrect tests, 129 Reference Java failures
r2- 300: 186 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 114 Reference Java failures
r4- 300: 184 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 116 Reference Java failures
r6- 300: 182 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 118 Reference Java failures
r1- 300: 175 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 125 Reference Java failures
r8- 300: 191 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 109 Reference Java failures
r11- 300: 174 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 126 Reference Java failures
r10- 300: 173 passed, 0 crashes, 0 fails, 0 hangs, 0 incorrect tests, 127 Reference Java failures

Finished at: Thu Sep 21 17:24:11 UTC 2023


[2023-09-21T17:24:11.504096611Z] Waiting for completion for process 15490
[2023-09-21T17:24:11.504397072Z] Waiting for completion finished for process 15490
----------System.err:(15/908)----------
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.reportResults(JavaFuzzerRunner.java:244)
	at applications.javafuzzer.JavaFuzzerRunner.runWithConfigurations(JavaFuzzerRunner.java:265)
	at applications.javafuzzer.JavaFuzzerRunner.main(JavaFuzzerRunner.java:283)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333)
	at java.base/java.lang.Thread.run(Thread.java:1570)

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


The summary above has this line:

r12- 300: 170 passed, 0 crashes, 2 fails, 0 hangs, 0 incorrect tests, 129 Reference Java failures

so we have two failures, but no obvious info about what those 
failures are... 

It has been a long time since I've seen a javafuzzer failure without 
hs_err_pid files.

This might be the same failure mode as this bug, but it's with a different test:

JDK-8316396 javafuzzer/MediumTest.java failed with "assertEquals: expected 1 to equal 2"

which had the synopsis updated to:

JDK-8316396 Endless loop in C2 compilation triggered by AddNode::IdealIL
Comments
It's a duplicate of JDK-8316396.
22-09-2023