Repository navigation
Conversation
Brings SWTBot coverage back to CI. Several UI tests currently fail for reasons that will take more extensive work to fix. This is a first step to get the suite running in CI so that new regressions are visible. The UI step runs under Xvfb with the metacity window manager. It has continue-on-error set and runs after packaging, so a UI failure never fails the job or blocks a build. Xvfb alone isn't enough. With no window manager, no shell ever becomes active, and SWTBot resolves widgets against Display.getActiveShell(), so every wait on shell activation (closeFile(), openDataObject(), ...) times out. The Linux CI job previously listed the HDF4 library directory only in LD_LIBRARY_PATH, and every HDF4 operation in the UI suite failed due to link errors. The tests get their library path from platform.hdf.lib, which becomes -Djava.library.path and replaces the JVM default, so LD_LIBRARY_PATH never mattered. The job now lists the HDF4 directory in platform.hdf.lib too, as the build.properties template and the Windows workflows already do. A summary step writes per-class test counts to the job summary.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings SWTBot coverage back to CI.
Several UI tests currently fail for reasons that will take more extensive work to fix. This is a first step to get the suite running in CI so that new regressions are visible.
The UI step runs under Xvfb with the metacity window manager. It has continue-on-error set and runs after packaging, so a UI failure never fails the job or blocks a build.
The CI tests also required the window manager metacity. With no window manager, no shell ever becomes active, and SWTBot resolves widgets against Display.getActiveShell(), so every wait on shell activation (closeFile(), openDataObject(), ...) times out.
The Linux CI job previously listed the HDF4 library directory only in LD_LIBRARY_PATH, and every HDF4 operation in the UI suite failed due to link errors. The tests get their library path
from platform.hdf.lib, which becomes -Djava.library.path and replaces the JVM default, so LD_LIBRARY_PATH never mattered. The job now lists the HDF4 directory in platform.hdf.lib too, as the build.properties template and the Windows workflows already do.
A summary step writes per-class test counts to the job summary.
Partially resolves #483