Don't run booster jobs on borked CI runners#2264
Draft
knoellle wants to merge 1 commit intoHULKs:mainfrom
Draft
Conversation
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Member
Author
|
Did not fix the issue, need to investigate further |
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
2 participants
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.
Why? What?
For some reason, building with the booster container fails on CI runner 1 and 3. No idea why.
Instead of disabling them outright, this PR just prevents these jobs from running on these specific runners but they can still do the other jobs.
Fixes #
ToDo / Known Issues
Ideas for Next Iterations (Not This PR)
Find out why CI is bronek in the first place
How to Test
See if CI runs correctly