JDK-8295104 : Break VarHandle tests into separate @test to reduce test execution time
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P4
  • Status: Resolved
  • Resolution: Withdrawn
  • Submitted: 2022-10-10
  • Updated: 2022-10-14
  • Resolved: 2022-10-14
Related Reports
Relates :  
JDK-8294147 - Review running times of java.lang.invoke regression tests
Description
The execution time of these VarHandle tests are long:
 
java/lang/invoke/VarHandles/VarHandleTestByteArrayAsInt.jtr 59303
java/lang/invoke/VarHandles/VarHandleTestByteArrayAsLong.jtr 44585
java/lang/invoke/VarHandles/VarHandleTestByteArrayAsFloat.jtr 34619
java/lang/invoke/VarHandles/VarHandleTestAccessLong.jtr 24176
java/lang/invoke/VarHandles/VarHandleTestAccessShort.jtr 23707
java/lang/invoke/VarHandles/VarHandleTestByteArrayAsDouble.jtr 23599
java/lang/invoke/VarHandles/VarHandleTestAccessChar.jtr 23275
java/lang/invoke/VarHandles/VarHandleTestAccessInt.jtr 22978
java/lang/invoke/VarHandles/VarHandleTestAccessByte.jtr 21701
java/lang/invoke/VarHandles/VarHandleTestAccessString.jtr 18969
Comments
Another approach is to consider what test cases need to run in -Xint and compile mode and how the test cases can be broken and the stress cases could be moved to other tiers.
14-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10641 Date: 2022-10-10 23:16:20 +0000
10-10-2022