On Thu, 24 Apr 2025 08:53:42 GMT, Kevin Walls <kev...@openjdk.org> wrote:
> 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. Update: Additionally, the log can still get huge and truncated due to many many lines like: hasMainArgs(21400): sun.jvmstat.monitor.MonitorException: Could not attach to 21400 ...so, only log such an Exception if it's NOT saying "Could not attach", as they are expected to be very common. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24843#issuecomment-2828646290
