Currently, jtreg prints following message when any of action fails in agentvm mode.
"result: Error. Agent error: java.lang.Exception: Agent 3 timed out with a timeout of 1200 seconds; check console log for any additional details "
This message is very confusing. It mentions "Agent error." so people might think about some Agen/Jtreg communication issues.
It would be better to describe the operation which timed out. At least to clearly set that it is not jtreg/agent problem but a timeout caused by issues with agentvm actions (run/compile).
"result: Error. Agent error: java.lang.Exception: Agent 3 timed out with a timeout of 1200 seconds; check console log for any additional details "
This message is very confusing. It mentions "Agent error." so people might think about some Agen/Jtreg communication issues.
It would be better to describe the operation which timed out. At least to clearly set that it is not jtreg/agent problem but a timeout caused by issues with agentvm actions (run/compile).
- relates to
-
CODETOOLS-7902347 There are no test result and test artifacts when test fails in agentvm mode
- New
-
JDK-8205526 tests timeout intermittently in "agentvm" mode
- Closed
- links to
-
Commit openjdk/jtreg/9d253be7
-
Review(master) openjdk/jtreg/205