JDK-8222418 : compiler/arguments/TestScavengeRootsInCode.java times out
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- CPU: x86_64
- Submitted: 2019-04-12
- Updated: 2019-05-08
- Resolved: 2019-04-17
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.
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 13 |
|---|
13 b17Fixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
he following test has started timing out in the jdk/jdk CI: compiler/arguments/TestScavengeRootsInCode.java so far on the MacOS X machines. Here's a snippet of the log file: #section:main ----------messages:(6/441)---------- command: main -XX:+UnlockDiagnosticVMOptions -Xcomp -XX:-TieredCompilation -XX:ScavengeRootsInCode=1 compiler.arguments.TestScavengeRootsInCode reason: User specified action: run main/othervm -XX:+UnlockDiagnosticVMOptions -Xcomp -XX:-TieredCompilation -XX:ScavengeRootsInCode=1 compiler.arguments.TestScavengeRootsInCode Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. elapsed time (seconds): 1238.954 ----------configuration:(0/0)---------- ----------System.out:(2/34)---------- Passed Timeout refired 1200 times ----------System.err:(1/15)---------- STATUS:Passed. ----------rerun:(43/5017)*---------- The test is using the default timeout value of 120 seconds/2 minutes and this task uses a default timeout factor of 10 so the total timeout value is 20 minutes. Notice that the test passed while the JTREG timeout handler was doing its work. Taking a quick look at CI results for this test, I see passes for this test in < 1 minute so I'm not sure why this test sometimes takes a long time.
Comments
|