RFR: 8318730: MonitorVmStartTerminate.java still times out after JDK-8209595 [v4]
Kevin Walls
kevinw at openjdk.org
Sun Apr 27 21:05:34 UTC 2025
> 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.
>
> While 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.
Kevin Walls has updated the pull request incrementally with one additional commit since the last revision:
remove file removal timeout, rely on jtreg timeout
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/24843/files
- new: https://git.openjdk.org/jdk/pull/24843/files/9423fc01..a1074954
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=24843&range=03
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=24843&range=02-03
Stats: 10 lines in 1 file changed: 0 ins; 9 del; 1 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
More information about the serviceability-dev
mailing list