-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Build] Replace use of coactions/setup-xvfb #1492
[Build] Replace use of coactions/setup-xvfb #1492
Conversation
bebd822
to
37d346a
Compare
The tests fail on Linux although XVFB is now available by default on the Linux runners: |
37d346a
to
5dea64c
Compare
5dea64c
to
a94fed2
Compare
a94fed2
to
2393795
Compare
@akurtakov do you have any idea why this fails with the preinstalled Could there be a version problem? |
2393795
to
7fd6585
Compare
See my comment here
|
daf4b2a
to
bb44f9a
Compare
Now that you have said it totally makes sense and it's obvious that it wasn't working with the initial attempt 🤦🏽♂️. In order to just prepend the xvfb-run command only on Linux I have used the 'ternay' operator for the GH action syntax: With that the Linux build now succeeds again without any test-failure. |
8e195b6
to
bb44f9a
Compare
The propertiy 'compare-version-with-baselines.skip' is true by default.
b804706
to
d687c1b
Compare
Because GH workflows running on Windows by default use 'PowerShell Core' as shell all arguments that contain a dot have to be quoted because powershell interprets dots. Running SWT on a 'CMD' shell breaks some tests.
d687c1b
to
9a66fef
Compare
Finally also the Windows workflow passes all tests. For some reasons, when using the |
Test failures in Jenkins are unrelated, submitting. |
Similar to eclipse-equinox/equinox#677.