On Mon, 31 Jan 2022 05:06:38 GMT, David Holmes <dhol...@openjdk.org> wrote:
> It may be an old issue but if we're using the wrong/inappropriate thread id > and that is what causes the current bug then it does seem very pertinent to > this PR. For a single "session" it doesn't matter which is used but if you > want an id that is valid across sessions then seems we should be using the > system id. Let me put it a different way. The thread ID issue an old bug that we are not going to address now (and likely not ever). This is a new test for a new command that is exposing the bug (there are other clhsdb commands that could have, but they are not testing in a sufficient manner to expose the bug). Therefore what makes sense now is to have the test work around the issue rather than fail. ------------- PR: https://git.openjdk.java.net/jdk/pull/7259
