On Wed, 14 Jun 2023 21:24:31 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> The test gets overloaded with MethodExitEvents, causing them to queue up (in > the JDI queue) and continue to be processed by the test after the debuggee > exits. This results in a VMDisconnectedException when the test tries to do > the following after getting an event: > > ` String str = ((MethodExitEvent)event).location().declaringType().name(); > ` > > The test is suppose to add filters to execlude events for all non-test > classes, but it is only filtering `java.*` and `sun.*`. There are also a very > large number of `jdk.*` events coming in, and this is what is causing the > event backlog and the processing of events after disconnect. Filtering out > `jdk.*` events reduces the total number of events to a few dozen, and the > test passes. > > More details can be found in the CR. > > Testing in progress: tier5 svc testing, and also running the failing test on > all platforms (both debug and product). This pull request has now been integrated. Changeset: 79ff72a7 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/79ff72a7762deb6010b57e5ac0ccede3d035ab4c Stats: 7 lines in 1 file changed: 5 ins; 0 del; 2 mod 8308499: Test vmTestbase/nsk/jdi/MethodExitRequest/addClassExclusionFilter/filter001/TestDescription.java failed: VMDisconnectedException Reviewed-by: lmesnik, kevinw ------------- PR: https://git.openjdk.org/jdk/pull/14480
