JDK-8213697 : compiler/graalunit/DebugTest.java fails in the jdk/jdk CI
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 12
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2018-11-09
  • Updated: 2023-07-21
  • Resolved: 2023-07-21
Related Reports
Duplicate :  
Description
The following test is failing in the jdk/jdk CI:

compiler/graalunit/DebugTest.java

Here's a snippet of the log file:

There was 1 failure:
1) test2(org.graalvm.compiler.debug.test.TimerKeyTest)
java.lang.ExceptionInInitializerError
	at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.serviceprovider.GraalServices.isCurrentThreadCpuTimeSupported(GraalServices.java:290)
	at org.graalvm.compiler.debug.test.TimerKeyTest.checkCapabilities(TimerKeyTest.java:50)
	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:567)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at com.oracle.mxtool.junit.MxJUnitWrapper.runRequest(MxJUnitWrapper.java:280)
	at com.oracle.mxtool.junit.MxJUnitWrapper.main(MxJUnitWrapper.java:196)
Caused by: java.lang.IllegalCallerException: jdk.vm.ci.common is not open to module jdk.internal.vm.compiler
	at java.base/java.lang.Module.addOpens(Module.java:762)
	at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.serviceprovider.GraalServices.openJVMCITo(GraalServices.java:120)
	at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.serviceprovider.GraalServices$1$1.next(GraalServices.java:95)
	at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.serviceprovider.GraalServices.loadSingle(GraalServices.java:142)
	at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.serviceprovider.JMXService.<clinit>(JMXService.java:51)
	... 31 more

FAILURES!!!
Tests run: 16,  Failures: 1
Comments
Is now closed as a duplicate of JDK-8213588. I just used the duplicate link that Dean had set on the bug. I didn't check it to make sure that it was the right bug. Sorry about that.
10-11-2018

Can you make it a duplicate of the real issue rather than changing to a bug that is itself closed as a duplicate. And how can this be fixed if the bug it "duplicates" is itself listed as a duplicate of a bug that is still open???
10-11-2018

Bugs in "Fixed" state must have an associated changeset. Will reclose as a duplicate.
09-11-2018

We are seeing this test multiple times in every jdk/jdk CI tier3 job set. Bumping the priority to P2.
09-11-2018