https://bz.apache.org/bugzilla/show_bug.cgi?id=69684
--- Comment #1 from [email protected] --- I just ran into this behavior unexpectedly when trying to understand why I wasn't getting parallel execution to work. I'm not sure how fixing this would work when combined with the `forkMode=perTestClass` option that was added in 1.10.14 though. That probably needs some special thinking. In the old JUnit 4 task this kind of thing was orchestrated by the task itself with the `forkMode` and `threads` attributes - it seems like under JUnitLauncher there's a very different division of responsibility, and it seems JUnit 5 itself does in-vm parallelism, rather than forking a new VM for each parallel run which can have unintended side-effects for tests which mutate global state. -- You are receiving this mail because: You are the assignee for the bug.
