You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_backspaceAndDelete StyledText and Text fail on I-build machine #2571
Multiple Failures (2 failures) java.lang.AssertionError: <no message> java.lang.RuntimeException: AwtScreenshot VM finished with exit code 1: Exception in thread "main" java.awt.AWTError: no screen devices at java.desktop/sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:101) at java.desktop/java.awt.Robot.<init>(Robot.java:135) at org.eclipse.test.AwtScreenshot.main(AwtScreenshot.java:43)
org.opentest4j.MultipleFailuresError: Multiple Failures (2 failures)
java.lang.AssertionError: <no message>
java.lang.RuntimeException: AwtScreenshot VM finished with exit code 1:
Exception in thread "main" java.awt.AWTError: no screen devices
at java.desktop/sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:101)
at java.desktop/java.awt.Robot.<init>(Robot.java:135)
at org.eclipse.test.AwtScreenshot.main(AwtScreenshot.java:43)
Suppressed: java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertTrue(Assert.java:53)
at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_custom_StyledText.test_backspaceAndDelete(Test_org_eclipse_swt_custom_StyledText.java:5916)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
Suppressed: java.lang.RuntimeException: AwtScreenshot VM finished with exit code 1:
Exception in thread "main" java.awt.AWTError: no screen devices
at java.desktop/sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:101)
at java.desktop/java.awt.Robot.<init>(Robot.java:135)
at org.eclipse.test.AwtScreenshot.main(AwtScreenshot.java:43)
at org.eclipse.test.AwtScreenshot.dumpAwtScreenshot(AwtScreenshot.java:113)
at org.eclipse.test.Screenshots.takeScreenshot(Screenshots.java:102)
at org.eclipse.test.Screenshots$ScreenshotOnFailure.failed(Screenshots.java:40)
Best guess is this fails because of UIPI issues - in the past the Windows machine needed a VNC client connected to it to allow test to work, see Bug 407862, but at some point all the other tests that do Display.post were disabled too so there is no visibility on it and we just haven't been testing Display.post consistently.
Therefore I am going to try to deal with any bitrotting in this area, and if I can't I will disable this test (at least on Jenkins/I-builds)
With #2576 merged test_postLorg_eclipse_swt_widgets_Event (in Test_org_eclipse_swt_widgets_Display) may fail on the I-build. If so, and I can't resolve the UIPI issues, then I will disable the tests on Jenkins.
cc: @iloveeclipse FYI because I know you often do triaging of new test failures and I wanted to make sure you knew what I am doing here.
A combination of further investigation on how UIPI and azure interact and celebrating my win so far here I have decided to proceed and just disable tests on non-GitHub actions.
Basically I think we would need to get the EF IT to have a permanent RDP connection to the Windows Azure dedicated machine so UIPI would allow SendEvent to work. There used to be a VNC connection to the Windows machine for this purpose in the distant past (see Bug 407862) but this seems to have long ago been abandoned, so when the transition was made to azure (when??) the functionality didn't carry over. By this point the tests requiring it had all been disabled, so no one took much notice. (Much of this paragraph is educated guessing and conjecture)
For the "celebrating my win" part, I started down this path of fixing the false positive test result in test_backspaceAndDelete as an exercise in learning SWT. These tests, and now the related test_postLorg_eclipse_swt_widgets_Event pass again, albeit only on GHA. This is the win and progress I am going to celebrate and close off this issue here with the merging of #2578
#2578 was not merged in time for the build (I20251001-1800) currently running, but if all goes to plan these tests will be skipped from the next I-build.
The test org.eclipse.swt.tests.junit.Test_org_eclipse_swt_widgets_Text.test_backspaceAndDelete() constently fails on MacOS, sometimes in GHA and is disabled on Jenkins. The ignore message is referencing this closed issue.
I think it should be ignored completely, or otherwise handled. Please reopen.
The test org.eclipse.swt.tests.junit.Test_org_eclipse_swt_widgets_Text.test_backspaceAndDelete() constently fails on MacOS, sometimes in GHA and is disabled on Jenkins. The ignore message is referencing this closed issue.
I think it should be ignored completely, or otherwise handled. Please reopen.
Thank you for sharing the reference! Then we should probably disable the test on macOS also for GHA in cas no one wants to investigate the failure and ensure functionality of the according behavior on macOS.
Activity
jonahgraham commentedon Oct 1, 2025
Best guess is this fails because of UIPI issues - in the past the Windows machine needed a VNC client connected to it to allow test to work, see Bug 407862, but at some point all the other tests that do Display.post were disabled too so there is no visibility on it and we just haven't been testing Display.post consistently.
Therefore I am going to try to deal with any bitrotting in this area, and if I can't I will disable this test (at least on Jenkins/I-builds)
jonahgraham commentedon Oct 1, 2025
Naturally this is connected to the other KeyEvent issues on GitHub actions 😢 #2516
Re-enable Display.post tests
jonahgraham commentedon Oct 2, 2025
With #2576 merged
test_postLorg_eclipse_swt_widgets_Event(in Test_org_eclipse_swt_widgets_Display) may fail on the I-build. If so, and I can't resolve the UIPI issues, then I will disable the tests on Jenkins.cc: @iloveeclipse FYI because I know you often do triaging of new test failures and I wanted to make sure you knew what I am doing here.
jonahgraham commentedon Oct 2, 2025
TL;DR
A combination of further investigation on how UIPI and azure interact and celebrating my win so far here I have decided to proceed and just disable tests on non-GitHub actions.
Basically I think we would need to get the EF IT to have a permanent RDP connection to the Windows Azure dedicated machine so UIPI would allow SendEvent to work. There used to be a VNC connection to the Windows machine for this purpose in the distant past (see Bug 407862) but this seems to have long ago been abandoned, so when the transition was made to azure (when??) the functionality didn't carry over. By this point the tests requiring it had all been disabled, so no one took much notice. (Much of this paragraph is educated guessing and conjecture)
For the "celebrating my win" part, I started down this path of fixing the false positive test result in
test_backspaceAndDeleteas an exercise in learning SWT. These tests, and now the relatedtest_postLorg_eclipse_swt_widgets_Eventpass again, albeit only on GHA. This is the win and progress I am going to celebrate and close off this issue here with the merging of #2578#2578 was not merged in time for the build (I20251001-1800) currently running, but if all goes to plan these tests will be skipped from the next I-build.
Disable Display.post tests if not running on GitHub actions
basilevs commentedon Apr 30, 2026
The test
org.eclipse.swt.tests.junit.Test_org_eclipse_swt_widgets_Text.test_backspaceAndDelete()constently fails on MacOS, sometimes in GHA and is disabled on Jenkins. The ignore message is referencing this closed issue.I think it should be ignored completely, or otherwise handled. Please reopen.
HeikoKlare commentedon May 4, 2026
Do you have a reference to a recent failure?
basilevs commentedon May 4, 2026
https://github.com/eclipse-platform/eclipse.platform.swt/actions/runs/24934011570/job/73016365667#step:8:3655
516ba1d
HeikoKlare commentedon May 5, 2026
Thank you for sharing the reference! Then we should probably disable the test on macOS also for GHA in cas no one wants to investigate the failure and ensure functionality of the according behavior on macOS.