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.
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.
- duplicates
-
JDK-8222511 compiler/arguments/TestScavengeRootsInCode.java fails with "Timeout refired 1200 times"
- Closed
- relates to
-
JDK-8214025 assert(t->singleton()) failed: must be a constant when ScavengeRootsInCode < 2
- Resolved
-
JDK-8207267 Enable tests which currently do not run with Java Graal to run with libgraal
- Open