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.
Despite JDK-8079642 is declared as fixed, vm/mlvm/meth/stress/compiler/deoptimize keeps timeouting
Comments
Fix request [11u]
I backport this for parity with 11.0.23-oracle.
No risk, only a test change.
Aslo backport for JDK-8233453.
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
The cause of the slowness is not related to deoptimization done by the test.
The following code from vm/mlvm/meth/stress/compiler/deoptimize/Test.java runs very slow in fastdebug
MHTransformationGen.createAndCallSequence(retVal, dataSnapshot, _mh, _finalArgs, true);
Here the results of running modified test with 40 threads where each thread just runs
MHTransformationGen.createAndCallSequence(...) once and exits.
product: 3.5 sec
fastdebug: 2m38 sec
24-05-2017
This is debug build issue.
On my 24 cpu machine the test takes 16 minutes using fastdebug build against 10 seconds using product build.
I will look more what is going on in case fastdebug build is used.
22-05-2017
ILW = test timeout, often, no workaround = MMH = P3