Bug ID: JDK-8233453 MLVM deoptimize stress test timed out

Versions (Unresolved/Resolved/Fixed)

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 11	JDK 14
11.0.23-oracleFixed	14 b27Fixed

vmTestbase/vm/mlvm/meth/stress/compiler/deoptimize/Test.java#id1 test failed due to timeout in the JDK14 CI.

#section:main
----------messages:(6/399)----------
command: main -XX:ReservedCodeCacheSize=100m vm.mlvm.meth.stress.compiler.deoptimize.Test -threadsPerCpu 2 -threadsExtra 2
reason: User specified action: run main/othervm -XX:ReservedCodeCacheSize=100m vm.mlvm.meth.stress.compiler.deoptimize.Test -threadsPerCpu 2 -threadsExtra 2 
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 1420.547
----------configuration:(0/0)----------
----------System.out:(5/286)----------
### TRACE 1: RNG seed = 4633555106628553396 (0x404db1d1e1cacab4)
### TRACE 1: RNG seed = 4633555106628553396 (0x404db1d1e1cacab4)
### TRACE 1: RNG seed = 4633555106628553396 (0x404db1d1e1cacab4)
### TRACE 1: RNG seed = 4633555106628553396 (0x404db1d1e1cacab4)
Timeout refired 960 times

Fix request [11u] I backport this for parity with 11.0.23-oracle. No risk, only a test change. Aslo backport for JDK-8166275. Test passes. SAP nightly testing passed.
19-12-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk11u-dev/pull/2407 Date: 2023-12-18 07:55:54 +0000
18-12-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk11u-dev/pull/2405 Date: 2023-12-18 07:33:40 +0000
18-12-2023
URL: https://hg.openjdk.java.net/jdk/jdk/rev/046f9512418b User: rraghavan Date: 2019-12-09 08:35:32 +0000
09-12-2019
RFR - http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2019-December/036312.html <webrev> - http://cr.openjdk.java.net/~rraghavan/8233453/webrev.00/
09-12-2019
I don't think this is related to JDK-8058176. If we run out of code cache space, a warning should be printed. Given that the normal execution time of that test is below 1 min (even on Sparc), it seems that we get stuck somewhere. A deadlock would also explain why it reproduces more often on Sparc machines with many cores.
22-11-2019
Updated ILW = Test times out, single test (tier3), no workaround = MMH = P3
19-11-2019
ILW = Test times out, single test (tier3) on SPARC, no workaround = MLH = P4
04-11-2019

Relates :	JDK-8221393 - ResolvedMethodTable too small for StackWalking applications
Relates :	JDK-8166275 - vm/mlvm/meth/stress/compiler/deoptimize keeps timeouting
Relates :	JDK-8231169 - Tests time out on Sparc in 11u
Relates :	JDK-8235485 - mlvm deoptimize stress test is slower with intermittent timeouts after the 8221393 fix