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.

@ptziegler ptziegler added this to the 1.23.0 milestone Dec 21, 2025
@github-actions
Copy link

github-actions bot commented Dec 21, 2025

Test Results

 2 720 files  +  680   2 720 suites  +680   10h 24m 29s ⏱️ + 1h 29m 12s
 7 018 tests +   14   6 958 ✅ +   12   58 💤 ± 0  0 ❌ ±0  2 🔥 +2 
28 072 runs  +7 060  27 836 ✅ +6 998  232 💤 +58  0 ❌ ±0  4 🔥 +4 

For more details on these errors, see this check.

Results for commit 25aa318. ± Comparison against base commit ca9718d.

♻️ This comment has been updated with latest results.

@ptziegler ptziegler force-pushed the rewrite-swtbot-test branch 15 times, most recently from 02a3592 to e9feebe Compare December 24, 2025 00:45
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.
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.

1 participant