RFR: 8300811: jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of SUSPEND_ALL
Chris Plummer
cjplummer at openjdk.org
Thu Feb 2 17:57:34 UTC 2023
On Thu, 2 Feb 2023 17:32:15 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:
> This PR does not document the type of pre-integration testing that was done
on these changes. We're seeing intermittent test failures in Mach5 Tier3 with
I ran all com/sun/jdi, nsk/jdb, nsk/jdi, and nsk/jdwp tests on all supported hosts multiple times, and ran tier1. What I didn't test were product builds, which is where the failures seem to be prevalent.
> Also, I think this fix is going to do a great job of "shaking the trees" and will reveal some tests that were passing by accident.
Yes, the tests that use jdb have always been sensitive to timing issues. Many fixes have been put in place in the past and the tests have been pretty stable for a while now.
-------------
PR: https://git.openjdk.org/jdk/pull/12152
More information about the serviceability-dev
mailing list