On Tue, 6 May 2025 23:24:48 GMT, Sergey Bylokhov <s...@openjdk.org> wrote:
> > I've updated the test to include logging and ran the test 200x without > > failures. I think it's ok to push the test with these changes so that if > > the test ever does fail again we can use the logs and analyze the problem. > > I meant to run the test 200 times with logging but no other changes to find > the root cause. The other changes to the test seems unnecessary at first > glance. the test operations are already synchronized and delayed when > necessary. I've reverted the test and added logging for the eventsCount. I've run the test thru mach5 again without failures 200x. For now adding logging to the test is probably sufficient for debugging if the failure happens again. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24885#issuecomment-2864135431
