JDK-8068440 : Test6857159.java times out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7,9
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2015-01-05
  • Updated: 2019-03-19
  • Resolved: 2015-02-03
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 8 JDK 9
8u202Fixed 9 b52Fixed
Related Reports
Duplicate :  
JDK-7172776 - Execution of compiler/c2/6857159/Test6857159.java takes too much time
Relates :  
JDK-8073159 - improve Test6857159.java
Relates :  
JDK-6857159 - local schedule failed with checkcast of Thread.currentThread()
Comments
@run shell was removed so the shell file is not needed any more. There was followup fix in JDK9 JDK-8073159 JDK8 backport contains both the fixes.
10-10-2018
I have raised JDK-8190450 as this fix is not backported to JDK 8. As I find that this issue still exists in JDK 8 as of a recent run, I created new issue. Is there any specific purpose or challenge because of which this is not backported to JDK8?
07-11-2017
verified by nightly testing
26-07-2017
I agree that we should not use script to run this test. Switch to WB utilities to check compilation success.
08-01-2015
Second compilation, from GC_Baseline-G1.2015-01-05-80 test.out, happens 360 sec later: 23293 1 b 3 Test6857159$ct0::run (16 bytes) 389756 2 b 4 Test6857159$ct0::run (16 bytes) 389758 1 3 Test6857159$ct0::run (16 bytes) made not entrant Normally test takes very little, for example in JPRT on SPARC: TEST: compiler/c2/6857159/Test6857159.java shell: 11.638 seconds or windows-32: TEST: compiler/c2/6857159/Test6857159.java shell: 11.0 seconds
08-01-2015
Looking at the history this has happened regularly since 2014-12-12. It looks like the timeout kills the shell script after 960 seconds, but the JVM continues to finish the test in 1426 seconds. The JVM log therefore indicates that the test has completed... We really should get rid of all these shell script tests.
07-01-2015