Convert test workflow to container-based testing #1208
Conversation
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
Refactor the CI workflow to build and run tests inside Docker containers instead of directly on GitHub runners. This adds support for testing on Fedora releases in addition to Ubuntu 22.04 and 24.04.
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.
Refactor the CI workflow to build and run tests inside Docker containers instead of directly on GitHub runners. This adds support for testing on Fedora releases in addition to Ubuntu 22.04 and 24.04.
Description
This change uses container images for tests so that platforms other than the ones provided directly by GitHub can be tested.
Testing in container images makes it easier to support a broader range of platforms, but more importantly it allows gef to test and adapt to changes in glibc, gcc, and Python as they are released, rather than re-synchronizing with those projects every two years.
Checklist