JDK-8197446 : [Graal] compiler/compilercontrol/directives/LogTest.java fails with particular seed
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2018-02-08
  • Updated: 2018-07-02
  • Resolved: 2018-02-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 11
11Resolved
Related Reports
Duplicate :  
JDK-8197453 - Add support of extra problem list
Relates :  
JDK-8181753 - Graal should support compiler directives
Description
compiler/compilercontrol/directives/LogTest.java fails when running in Graal JIT mode with jdk.test.lib.random.seed=-4502076218740659163

java.lang.RuntimeException: Compilation log expected. Met: <task_done success='1' nmsize='40' count='600' stamp='4.954'/>: expected false, was true
	at jdk.test.lib.Asserts.fail(Asserts.java:594)
	at jdk.test.lib.Asserts.assertFalse(Asserts.java:461)
	at compiler.compilercontrol.share.processors.LogProcessor.matchTasks(LogProcessor.java:108)
	at compiler.compilercontrol.share.processors.LogProcessor.accept(LogProcessor.java:77)
	at compiler.compilercontrol.share.processors.LogProcessor.accept(LogProcessor.java:47)
	at compiler.compilercontrol.share.scenario.Scenario.lambda$execute$0(Scenario.java:116)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1395)
	at compiler.compilercontrol.share.scenario.Scenario.execute(Scenario.java:116)
	at compiler.compilercontrol.share.SingleCommand.test(SingleCommand.java:55)
	at compiler.compilercontrol.directives.LogTest.main(LogTest.java:45)
	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:564)
	at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:229)
	at java.base/java.lang.Thread.run(Thread.java:844)
Comments
Right, I've added a link to JDK-8197453.
02-07-2018
Thanks for the explanation Tobias! I think it would be more clear if this bug was closed as a duplicate of the change that problemlisted the tests for Graal.
02-07-2018
The test is not Graal but C1/C2 specific and just fails when being executed with Graal. The corresponding tests were problem listed for Graal until JDK-8181753 is implemented.
02-07-2018
It seems weird to me that a test failure is a duplicate of an enhancement. If this is not supported yet, then why are we testing it? The bug is in the test that is testing non-supported features.
30-06-2018
The method which misses a compilation log was Graal compiled but Graal does not support compiler directives. This is a duplicate of JDK-8181753.
09-02-2018
Steps to reproduce: > jtreg -vt -jdk:JDK_HS_fastdebug -vmoptions:-XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+TieredCompilation -XX:+UseJVMCICompiler -Djvmci.Compiler=graal -Djdk.test.lib.random.seed=-4502076218740659163 -dir:test/hotspot/jtreg compiler/compilercontrol/directives/LogTest.java
08-02-2018