On Fri, 25 Apr 2025 06:10:46 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> As part of the work for > [JDK-8353955](https://bugs.openjdk.org/browse/JDK-8353955) I am reducing the > number of tests that need to be run with includevirtualhreads=y due to using > JDI to lookup threads in the debuggee. There are many tests that lookup the > "main" thread. They can instead glean the "main" thread from the > ClassPrepareEvent for the debuggee main class. Some tests already wait for > this ClassPrepareEvent, and can take advantage of it. Most do not, but can be > made to do so. The easiest way to do this for many of the tests is to wait > for the event in Debuggee.prepareDebuggee() after having called > Debuggee.bindToDebuggee(). For tests that don't call > Debuggee.prepareDebuggee(), waiting for the ClassPrepareEvent was added after > the bind. This doesn't seem to have any ill affect on the tests. > > Tested by running all nsk/jdi tests, including all tier2, tier3, and tier5 > nsk/jdi testing. This pull request has now been integrated. Changeset: e2ae50d8 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/e2ae50d877b13b121912e2496af4b5209b315a05 Stats: 165 lines in 38 files changed: 75 ins; 15 del; 75 mod 8355569: Some nsk/jdi tests can glean the "main" thread by using the ClassPrepareEvent for the debuggee main class Reviewed-by: sspitsyn, amenkov ------------- PR: https://git.openjdk.org/jdk/pull/24867
