pnowojski commented on PR #28608: URL: https://github.com/apache/flink/pull/28608#issuecomment-4874362666
> The scaled variant on the reproducer branch makes the race reachable on a laptop (hundreds of timers per slice boundary + a throttled sink). There the A/B is: without the fix 6 of 7 batches of 5 runs contain at least one failure; with the fix 0 failures in 10 batches (50 runs). I wonder if we should add such "stress" ITCase back into the code base? If it's just a couple of parameters changed, and it doesn't take long to complete, I think that might be worthwhile. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
