JDK-8180723 : Compiler RTM tests fail
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8,9,10
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • Submitted: 2017-05-19
  • Updated: 2019-09-13
  • Resolved: 2019-07-01
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 13
13Resolved
Related Reports
Relates :  
JDK-8183263 - compiler/rtm tests fail on SKL hosts
Relates :  
JDK-8184800 - Streamline RTM flag validity testing with generic flag testing support
Relates :  
JDK-8181124 - Get rid of compiler.testlibrary.rtm.predicate
Relates :  
JDK-8184031 - compiler/rtm/locking/TestRTMAfterNonRTMDeopt.java fails on Windows
Description
The rtm locking tests failed during JDK8u141 b07 testing on the host stt-139.
There were no such failures observed before because tests just silently skip execution on most of hosts in our lab. Since RTM are not supported on them.

Leaving this as P4 issues since RTM locking is not supported yet.
Comments
These tests are not problem listed. Tests history doesn't show the tests failures as well. So looks like the tests don't fail anymore. Closing as non reproduceble.
01-07-2019
We should not throw all different failures into one bug. Each failure type should have separate bug I think.
27-07-2017
Some failed RTM flags check tests were removed when flags range checks were added by JDK-8184800.
27-07-2017
Thank you!
30-05-2017
Vladimir, I fix compiler/rtm/cli/TestRTMAbortRatioOptionOnUnsupportedConfig.java and compiler/rtm/cli/TestRTMTotalCountIncrRateOptionOnUnsupportedConfig.java which starts fail after JDK-8180612 as part of JDK-8181124 change. I am going to send for review today.
30-05-2017
Recently pushed JDK-8180612 changes may cause next RTM tests failures: compiler/rtm/cli/TestRTMAbortRatioOptionOnUnsupportedConfig.java stderr: [int RTMAbortRatio=200 is outside the allowed range [ 0 ... 100 ] Improperly specified VM option 'RTMAbortRatio=200' Error: Could not create the Java Virtual Machine. compiler/rtm/cli/TestRTMTotalCountIncrRateOptionOnUnsupportedConfig.java stderr: [int RTMTotalCountIncrRate=-1 is outside the allowed range [ 1 ... 2147483647 ] Improperly specified VM option 'RTMTotalCountIncrRate=-1' Error: Could not create the Java Virtual Machine.
27-05-2017
Hi Ekaterina [~epavlova], this issue is related to the RTM tests (just as JDK-8181124, which is also assigned to you). Could you please look at this issue as well? There may be some overlap between the two issues -- it could be best to handle those at the once. Thank you! Zoltan
26-05-2017
My machine has a CPU of type Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz. Documentation [1] indicates that the TSX-NI is not available on this CPU. (At least that's what the "Intel�� TSX-NI No" line suggests to me.) The RTM tests are nevertheless executed on my system, some of them fail. FAILED: compiler/rtm/locking/TestRTMAbortRatio.java#id0 FAILED: compiler/rtm/locking/TestRTMAbortThreshold.java#id0 FAILED: compiler/rtm/locking/TestRTMAfterNonRTMDeopt.java#id0 FAILED: compiler/rtm/locking/TestRTMDeoptOnHighAbortRatio.java#id0 FAILED: compiler/rtm/locking/TestRTMDeoptOnLowAbortRatio.java#id0 FAILED: compiler/rtm/locking/TestRTMLockingCalculationDelay.java#id0 FAILED: compiler/rtm/locking/TestRTMLockingThreshold.java#id0 FAILED: compiler/rtm/locking/TestUseRTMXendForLockBusy.java#id0 FAILED: compiler/rtm/print/TestPrintPreciseRTMLockingStatistics.java#id0 (I used the 9 codebase.) The question now is whether these are test-related problems or problems due to the feature. Also, I'm not sure if my machine has the buggy RTM feature [2]. [1] http://ark.intel.com/products/76347/Intel-Core-i5-4300M-Processor-3M-Cache-up-to-3_30-GHz [2] https://en.wikipedia.org/wiki/Transactional_Synchronization_Extensions#Implementation
22-05-2017
ILW=incorrect behavior (either test/environment is incorrect or feature is incorrect), few (~10) tests affecting feature disabled by default, feature can be disabled (and is disabled by default)=HLL=P4
22-05-2017
It would be nice to fix test definitions to always execute RTM related tests on the hosts which support RTM instructions to find such issues earlier.
19-05-2017
Link to the failure: http://aurora.us.oracle.com/functional/faces/RunDetails.xhtml?names=2285155.ute.st2-2 RULE "compiler/rtm/locking/TestRTMAbortThreshold.java" Exception java.lang.RuntimeException: Expected that method with rtm lock elision was deoptimized after ... lock attempts RULE "compiler/rtm/locking/TestRTMAfterNonRTMDeopt.java" Exception java.lang.RuntimeException: VM output should contain ... RTM locking statistics entries. RULE "compiler/rtm/locking/TestRTMDeoptOnHighAbortRatio.java" Exception java.lang.RuntimeException: VM output should contain exactly one RTM locking statistics entry for method rtm.XAbortProvoker::forceAbort RULE "compiler/rtm/locking/TestRTMLockingThreshold.java" Exception java.lang.RuntimeException: VM output should contain two RTM locking statistics entries. RULE "compiler/rtm/locking/TestRTMTotalCountIncrRate.java" Exception java.lang.RuntimeException: VM output should contain exactly one RTM locking statistics entry for method TestRTMTotalCountIncrRate$Test::lock RULE "compiler/rtm/locking/TestUseRTMAfterLockInflation.java" Exception java.lang.RuntimeException: Total lock count should be greater or equal to ... RULE "compiler/rtm/locking/TestUseRTMForInflatedLocks.java" Exception java.lang.RuntimeException: Total lock count should be greater or equal to ... RULE "compiler/rtm/locking/TestUseRTMForStackLocks.java" Exception java.lang.RuntimeException: Total locks count should be greater or equal to ... RULE "compiler/rtm/method_options/TestUseRTMLockElidingOption.java" Exception java.lang.RuntimeException: Expected to get total locks count equal to total amount of lock attempts. RULE "compiler/rtm/print/TestPrintPreciseRTMLockingStatistics.java" Exception java.lang.RuntimeException: RTM locking statistics should contain non zero total locks count
19-05-2017