On Fri, 19 Sep 2025 09:27:47 GMT, Prasanta Sadhukhan <[email protected]> wrote:
>> Test used to timeout even though it seems the test passed..Increased the >> timeout to a safe value as sometimes it shows elapsed time to timeout > >> 300secs in macOS in CI and also ensured the wait-time for child process to >> execute the test is not been waiting endlessly. >> Also ensured the original display mode is resetted after the test to prevent >> affecting following tests. >> >> Tried 100 iterations of the fix on all platforms which is ok > > Prasanta Sadhukhan has updated the pull request incrementally with one > additional commit since the last revision: > > EDT fix, timeout reduced >I think you may have missed the point as to why this test is unstable. >Look at all the code running on the EDT which constructs the UI that should be >either not run there or should be in separate calls. So what exactly is the reason the test is unstable? How does executing all that code in a single invokeAndWait call cause it to hang on only one platform? ------------- PR Comment: https://git.openjdk.org/jdk/pull/27365#issuecomment-3313801660
