JDK-8367599 : SWTCursorsTest fails intermittently
  • Type: Bug
  • Component: javafx
  • Sub-Component: other
  • Affected Version: jfx26
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: linux,os_x
  • CPU: generic
  • Submitted: 2025-09-13
  • Updated: 2025-10-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
JDK-8356688 enabled the SWT tests on Linux.

The following test failed one time on our headful Ubuntu 22.04 system:


> Task :swt:test FAILED

SWTCursorsTest > testImageCursor() FAILED
    org.opentest4j.AssertionFailedError: expected: not <null>
        at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
        at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
        at app//org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
        at app//org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
        at app//org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
        at app//org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
        at app//test.javafx.embed.swt.SWTCursorsTest.lambda$testImageCursor$1(SWTCursorsTest.java:65)
        at app//org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
        at app//org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132)
        at app//org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5039)
        at app//org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4519)
        at app//test.javafx.embed.swt.SWTCursorsTest.lambda$testImageCursor$0(SWTCursorsTest.java:71)
        at app//test.javafx.embed.swt.SWTTest.lambda$runOnSwtThread$0(SWTTest.java:52)
        at app//org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
        at app//org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132)
        at app//org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5039)
        at app//org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4519)
        at app//test.javafx.embed.swt.SWTTest.runOnSwtThread(SWTTest.java:62)
        at app//test.javafx.embed.swt.SWTCursorsTest.testImageCursor(SWTCursorsTest.java:50)

Comments
We dont run CI tests on Windows hardware, so this test basically is not running on windows platform. So we will be disabling this test on all platforms under JDK-8368375.
23-09-2025

SWT tests were enabled under JDK-8169285 but they were skipped on macOS and Linux. They were enabled for macOS and Linux under JDK-8356687 & JDK-8356688. We are not seeing this SWT test failing in Windows. So i will disable this test only for macOS and Linux.
23-09-2025

I was testing macOS 26 and I also see this test fail about 1/4 of the time. I'm removing "Linux" from the title since it also fails on macOS sometimes. I recommend that we skip this test until we can stabilize it.
22-09-2025

This is mostly identified as infra/machine issue. The infra issue is rectified and if we don't see this test failing anymore by end of this week, we can close this issue.
16-09-2025

While testing the fix for JDK-8169285 a few months ago, I also saw the same failure, and commented on it in the PR: https://github.com/openjdk/jfx/pull/1783#issuecomment-2828275978 As a result (and also because of a potential crash on Wayland), the Linux tests were not enabled at that time, but later were enabled via JDK-8356688 This suggests that SWTCursorsTest might be unstable on Ubuntu 22.04. We will need to keep a close eye on this test. If it fails again, we will either need to fix it or else file a new bug to skip it on Linux until it is fixed.
13-09-2025