ci: Reduce parallelism of vmcheck tests to 5 #3640
Merged
Conversation
This file contains 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
We're seeing issues where CI sometimes hits EAGAIN on `fork`: coreos/fedora-coreos-tracker#1186 It's possible something changed recently that made rpm-ostree use more threads than before and more likely to hit this. There's no way for us control the PID limit from our side (it's a node setting), so let's just lower parallelism here. (Another approach is splitting it into multiple pods, but it doesn't seem worth the complexity yet.)
cgwalters
approved these changes
Apr 27, 2022
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.
We're seeing issues where CI sometimes hits EAGAIN on
fork:coreos/fedora-coreos-tracker#1186
It's possible something changed recently that made rpm-ostree use more
threads than before and more likely to hit this.
There's no way for us control the PID limit from our side (it's a
node setting), so let's just lower parallelism here. (Another approach
is splitting it into multiple pods, but it doesn't seem worth the
complexity yet.)