Skip to content

Conversation

@ptziegler
Copy link
Contributor

Newer Eclipse versions no longer launch a workspace when running a test outside the UI thread. Because this is a requirement for all of our SWTBot tests, we can no longer run them locally.

The tests were originally written like that because they open a modal dialog and would thus lead to a deadlock if the test is also executed within the UI thread. But thanks to the changes to the UiContext, we have a way to make this work regardless.

@github-actions
Copy link

github-actions bot commented Jan 22, 2026

Test Results

 2 700 files   - 13   2 700 suites   - 13   10h 24m 59s ⏱️ - 29m 9s
 6 982 tests  - 22   6 923 ✅  - 21   58 💤 ±0  0 ❌  - 1  1 🔥 ±0 
27 928 runs   - 52  27 682 ✅  - 54  242 💤 ±0  0 ❌  - 1  4 🔥 +3 

For more details on these errors, see this check.

Results for commit f5af11d. ± Comparison against base commit 860f827.

This pull request removes 36 and adds 14 tests. Note that renamed tests count towards both.
WindowBuilderTests RcpTests WizardTests Eclipse4WizardTest ‑ testCreateNewViewPart
WindowBuilderTests RcpTests WizardTests Eclipse4WizardTest ‑ testCreateNewViewPartNoSelection
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewApplicationWindow
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewApplicationWindowNoSelection
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewDialog
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewDialogNoSelection
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewTitleAreaDialog
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewTitleAreaDialogNoSelection
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewWizard
WindowBuilderTests RcpTests WizardTests JFaceWizardTest ‑ testCreateNewWizardNoSelection
…
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewApplicationWindow
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewApplicationWindowNoSelection
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJApplet
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJAppletNoSelection
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJDialog
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJDialogNoSelection
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJFrame
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJFrameNoSelection
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJInternalFrame
WindowBuilderTests SwingTests WizardTests SwingNewWizardTest ‑ testCreateNewJInternalFrameNoSelection
…

♻️ This comment has been updated with latest results.

Newer Eclipse versions no longer launch a workspace when running a test
outside the UI thread. Because this is a requirement for all of our
SWTBot tests, we can no longer run them locally.

The tests were originally written like that because they open a modal
dialog and would thus lead to a deadlock if the test is also executed
within the UI thread. But thanks to the changes to the `UiContext`, we
have a way to make this work regardless.
@ptziegler ptziegler force-pushed the rewrite-swtbot-swing-test branch from 5744670 to f5af11d Compare January 22, 2026 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants