ci: increase CPU request to 1 and disable concurrent builds #688
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
Signed-off-by: Esteban Laver <10552966+emlaver@users.noreply.github.com>
ricellis
approved these changes
Jan 12, 2024
eiri
approved these changes
Jan 12, 2024
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.
Checklist
CHANGES.md) or test/build only changesDescription
The fatal error unit tests failed right before the merge of #662.
This most likely happened when our kube CI resources were strained and being throttled . Increasing the CPU request to 1 and disabling concurrent builds should hopefully allow for enough resources so that the test suite doesn't time out.
fixes i316
Approach
Schema & API Changes
Security and Privacy
Testing
Monitoring and Logging