On Fri, 30 May 2025 03:15:40 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
>> Based on the log output, the test failure seems to be the result of two >> threads trying to set and access variables that are not volatile, so I've >> made them volatile. Since I can't reproduce the failure, I can't confirm >> that it is now fixed, but the lack of volatile is clearly a bug so should be >> done anyway. Tested by running the test locally to make sure nothing breaks. > > Chris Plummer has updated the pull request incrementally with one additional > commit since the last revision: > > cleaned up event counters I filed [JDK-8358172](https://bugs.openjdk.org/browse/JDK-8358172) to improve this test w.r.t. properly testing that that 2nd exception is uncaught. ------------- PR Comment: https://git.openjdk.org/jdk/pull/25236#issuecomment-2923037831
