JDK-8201333 : [Graal] compiler/jvmci/compilerToVM/ReprofileTest.java fails when running with Graal as JIT
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11,13,14,15
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2018-04-09
  • Updated: 2020-07-09
  • Resolved: 2020-07-09
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 15
15Resolved
Related Reports
Duplicate :  
JDK-8207267 - Enable tests which currently do not run with Java Graal to run with libgraal
Relates :  
JDK-8199624 - [Graal] Blocking jvmci compilations time out
Description
---------System.out:(2/141)----------
public int compiler.jvmci.compilerToVM.DummyClass.dummyInstanceFunction()
public void compiler.jvmci.compilerToVM.DummyClass.dummyFunction()
----------System.err:(18/1652)----------
java.lang.RuntimeException: public void compiler.jvmci.compilerToVM.DummyClass.dummyFunction() : profiling info wasn't changed after 150000 invocations: expected DefaultProfilingInfo<> to not equal DefaultProfilingInfo<>
	at jdk.test.lib.Asserts.fail(Asserts.java:594)
	at jdk.test.lib.Asserts.assertNotEquals(Asserts.java:394)
	at jdk.test.lib.Asserts.assertNE(Asserts.java:367)
	at compiler.jvmci.compilerToVM.ReprofileTest.runSanityTest(ReprofileTest.java:101)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1395)
	at compiler.jvmci.compilerToVM.ReprofileTest.main(ReprofileTest.java:64)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115)
	at java.base/java.lang.Thread.run(Thread.java:831)
Comments
The test is already listed in ProblemList-graal.txt. Closing this bug as duplicate of 8207267
09-07-2020
[~epavlova], since you were working on cleaning up Graal testing and consolidation of known failures under umbrella bugs, I'm assigning this and some other unassigned Graal (alleged) test bugs to you.
02-07-2020
I did more debugging and the issue seems is not related to JDK-8199624. The tested method is not getting compiled over time at all.
11-04-2018
ILW = ReprofileTest jvmci test failure due to Graal compilation not blocking; with graal as jit, intermittent; disable Graal! = MLM = P4 As part of old JDK-8199624 timeout value for blocking jvmci compilations was increased and corresponding WhiteBox API changed to return false if compilation does not block and times out. So may be similar to done for selected tests in JDK-8199624, here also fix is to catch and ignore the timeout in the affected test!? Labeling this one as testbug for now.
11-04-2018
The issue seems to be similar to JDK-8199624. I added method.hasCompiledCode() check into ReprofileTest.java > diff -r 450d709262c1 test/hotspot/jtreg/compiler/jvmci/compilerToVM/ReprofileTest.java --- a/test/hotspot/jtreg/compiler/jvmci/compilerToVM/ReprofileTest.java Fri Apr 06 09:59:48 2018 -0400 +++ b/test/hotspot/jtreg/compiler/jvmci/compilerToVM/ReprofileTest.java Mon Apr 09 13:28:26 2018 -0700 @@ -96,8 +96,9 @@ } catch (ReflectiveOperationException e) { throw new Error("TEST BUG : " + e.getMessage(), e); } + System.out.println("method.hasCompiledCode: " + method.hasCompiledCode()); ProfilingInfo compProfile = method.getProfilingInfo(); - + Asserts.assertNE(startProfile.toString(), compProfile.toString(), String.format("%s : profiling info wasn't changed after " + "%d invocations", and I see that method.hasCompiledCode() returns false in case of the test failure.
09-04-2018