On Tue, 23 Sep 2025 06:17:51 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: > > PL updation test/jdk/ProblemList.txt line 259: > 257: > 258: > sun/java2d/X11SurfaceData/SharedMemoryPixmapsTest/SharedMemoryPixmapsTest.sh > 7184899,8221451 linux-all,macosx-aarch64 > 259: java/awt/FullScreen/DisplayChangeVITest/DisplayChangeVITest.java 8169469 > windows-all,macosx-aarch64 So does this test really still fail on macos ARM ? The only remaining bug ID is entirely about windows. Seems you should remove the arm entry and re-test and it if does fail, then maybe a new bug is needed. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/27365#discussion_r2376891361
