Build and test against MacOS

[ptziegler]

No description provided.

[github-actions]

Test Results

     7 files  +    3       7 suites  +3   2h 23m 25s ⏱️ + 16m 15s
 7 022 tests ±    0   6 978 ✅  -    14   30 💤 ±  0  11 ❌ +11  3 🔥 +3 
29 611 runs  +5 927  28 981 ✅ +5 393  606 💤 +510  21 ❌ +21  3 🔥 +3 

For more details on these failures and errors, see this check.

Results for commit ee259bd. ± Comparison against base commit a799d4b.

♻️ This comment has been updated with latest results.

[ptziegler]

The MacOS test runner is running on ARM64, so none of the SWT tests will be successful. See #1622.

[ptziegler]

The runner doesn't seem to register that new extensions were added and gets stuck in a busy loop. I've added a timeout so that the job will hopefully be able to finish.

[ptziegler]

Then runner seems to get stuck on MacOS quite a lot. And every time, it seems to be related to the creation of a JFrame. It wouldn't surprise me if this somehow triggers a popup or something that prevents the test from continuing...

[ptziegler]

As an alternative hypothesis, it might be a conflict between the SWT UI thread and the Swing event dispatcher. They are also competing on Linux, which frequently causes issues. But not to that extent.

[ptziegler]

[macos] Swing app fails when using -XstartOnFirstThread