On Wed, 28 May 2025 16:47:55 GMT, Alexey Ivanov <aiva...@openjdk.org> wrote:
>>> Re: expected=ff000000 actual=ffffffff — I can't see a while pixel on the >>> screenshot. >> >> This is screenshot of the frame when the test passes. Added it to show what >> the Frame looks like when the test passes. >> >>> Does the test save both images: the expected and the actual one? >> >> No it doesn't. The updated test saves the frame and the whole screen (I >> wanted to see if there are any stray windows overlapping the test frame). >> Since I haven't gotten the test to fail on personal CI job, I thought it >> might be a good idea to de-problemlist the test and see what is going on. > >> > Does the test save both images: the expected and the actual one? >> >> No it doesn't. The updated test saves the frame and the whole screen (I >> wanted to see if there are any stray windows overlapping the test frame). >> Since I haven't gotten the test to fail on personal CI job, I thought it >> might be a good idea to de-problemlist the test and see what is going on. > > You can test it by submitting a test job without integrating these changes. > > You can do it with the test in its original form where the UI is created on > the main thread rather than EDT. The personal CI job that was referring to was with the original test + screenshot capture. IIRC it did not fail during those runs. I have triggered another round of testing with original test + MultiResolution screen capture as suggested to see if the test failure is reproducible. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/25279#discussion_r2112475497
