On Wed, 23 Nov 2022 02:28:02 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> Do you plan on closing the CRs associated with these changes even though the > root causes are not being addressed, just avoided? These two CRs are like ProblemListing bugs: [JDK-8297367](https://bugs.openjdk.org/browse/JDK-8297367): disable TestRedirectLinks.java in slowdebug mode [JDK-8297369](https://bugs.openjdk.org/browse/JDK-8297369): disable Fuzz.java in slowdebug mode They are both sub-tasks of the bugs that describe the slowdebug failures that I'm seeing. So the "disable" bugs will be closed if/when I integrate these work arounds much like a ProblemListing bug is closed when a test is added to a ProblemList. However, the parent bugs will remain open so that someone can investigate and fix these slowdebug issue in the future. > It's not clear what is meant by "Test is unstable". Is the test buggy, or are > these JVM issues? I suspect that the tests have inherent assumptions about how long things take to happen and they don't happen "on time" when slowdebug bits are used. > In either case shouldn't we be trying to understand why it is unstable with > slowdebug bug not fastdebug? Yes and that's why the parent bugs will still be open. This is just like ProblemListing a test when it is too noisy in the CI. However, in this case, these tests are being disabled in slowdebug configs instead of being ProblemListed for all configs. These two parent issues only affect folks running the tests in slowdebug configs when the system is heavily stressed. As far as I know, I'm the only person that regularly runs slowdebug testing... :-) ------------- PR: https://git.openjdk.org/jdk/pull/11278
