Fix gentoo CI build #4211
Merged
Fix gentoo CI build #4211
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
Rebuilding the gentoo docker image daily is most definitely going to bust through the free CI tier limits.
|
@Alexays could you run the docker workflow? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The gentoo CI job started started failing on recent PRs. What caught my attention is that it's running a pretty old version of gcc (12.2.1). Turns out the docker image hasn't been updated in nearly 2 years (most likely because of the strict version requirement for
dev-cpp/gtkmm).I've reduced the frequency of the docker build workflow, as a daily rebuild of the gentoo image will most certainly bust through the free CI tier. I've also added a
workflow_dispatchtrigger, so it can be run manually if needed.