On Wed, 5 Aug 2026 20:10:58 GMT, Chris Plummer <[email protected]> wrote:
> I like the overall approach. I think most of the new code you added can be > moved to a JdbTest API that is called from the test. Maybe you just pass in > the method name and the number of threads expected. Done. the loop now lives in JdbTest.waitForTestedThreadStarts(threadStartedMethod, expectedThreads), called by the seven tests after setting their lastBreak breakpoint. One thing the move surfaced: interrupt001 was the only one of the seven that never set the lastBreak field in main() (it predates this PR and the inline code used the local constant), which made the helper’s exit match trivially so I fixed that by adding the assignment like its siblings, and the helper now fails fast if lastBreak is unset ------------- PR Comment: https://git.openjdk.org/jdk/pull/32142#issuecomment-5199105998
