This issue was hard to reproduce or had stopped happening, but was likely a failure to capture the main arguments from a monitored process, caused by slow startups e.g. -Xcomp. Recent failures seen in Graal testing are most likely the same issue and increasing ARGS_ATTEMPTS has been seen to resolve it.
Whlie updating the test, fix the very verbose logging: it doesn't need to log, every second, how many nanos it has waited. This has made logs from timeouts hardly usable as they are truncated and may miss critical info. Also, group the "tunable" constants together. ------------- Commit messages: - JDK-8318730: MonitorVmStartTerminate.java still times out after JDK-8209595 Changes: https://git.openjdk.org/jdk/pull/24843/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=24843&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8318730 Stats: 10 lines in 1 file changed: 5 ins; 3 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/24843.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/24843/head:pull/24843 PR: https://git.openjdk.org/jdk/pull/24843
