-
Bug
-
Resolution: Fixed
-
P4
-
8, 9
-
b44
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083308 | emb-9 | Chris Plummer | P4 | Resolved | Fixed | team |
JDK-8265639 | openjdk8u302 | Chris Plummer | P4 | Resolved | Fixed | b01 |
If you submit a jprt job and use the -rtest option to run regression tests, they will likely timeout on slower devices, especially simulator devices. This will happen during the javac compilation of the test. Tests that don't need compilation don't seem to have this problem. Also, it doesn't always happen, so it seems that we are right on the border of whether or not it will timeout.
The fix is to increase the timeout buy adding the following to hotspot/test/Makefile:
# Multiply by 4 the timeout factor
JTREG_TIMEOUT_OPTION = -timeoutFactor:4
JTREG_BASIC_OPTIONS += $(JTREG_TIMEOUT_OPTION)
Note that this is already in jdk/test/Makefile, and running tests in jdk/test does not have the simulator timeout issue during javac compilation.
The fix is to increase the timeout buy adding the following to hotspot/test/Makefile:
# Multiply by 4 the timeout factor
JTREG_TIMEOUT_OPTION = -timeoutFactor:4
JTREG_BASIC_OPTIONS += $(JTREG_TIMEOUT_OPTION)
Note that this is already in jdk/test/Makefile, and running tests in jdk/test does not have the simulator timeout issue during javac compilation.
- backported by
-
JDK-8083308 JTReg tests timeout on slow devices when run using JPRT
-
- Resolved
-
-
JDK-8265639 JTReg tests timeout on slow devices when run using JPRT
-
- Resolved
-