-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(e2e): Use parallel tests for providers other than Docker #787
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
dlipovetsky
approved these changes
Jul 9, 2024
jimmidyson
force-pushed
the
jimmi/refactor-e2e-loops
branch
2 times, most recently
from
July 15, 2024 18:30
076d423
to
051d397
Compare
Keep Docker using serial tests to not exhaust resources of the machine that the Docker tests are running on. Other providers do not require so many resources as they use cloud or external infrastructure for clusters.
jimmidyson
force-pushed
the
jimmi/refactor-e2e-loops
branch
from
July 16, 2024 14:49
9ca2865
to
cb3277d
Compare
supershal
reviewed
Jul 16, 2024
supershal
approved these changes
Jul 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Merged
jimmidyson
added a commit
that referenced
this pull request
Jul 18, 2024
🤖 I have created a release *beep* *boop* --- ## 0.13.0 (2024-07-18) <!-- Release notes generated using configuration in .github/release.yaml at main --> ## What's Changed ### Exciting New Features 🎉 * feat: Secure ciphers, min TLS v1.2, and disable auto TLS for etcd by @jimmidyson in #808 * feat: Bump default k8s version for tests to v1.29.6 by @jimmidyson in #784 ### Fixes 🔧 * fix: add omitempty to addon strategy by @dkoshkin in #795 * fix: update CCM to 0.3.4 to fix sweet32 issue by @tuxtof in #805 * fix: Clean up MetalLB pod security standards labels by @jimmidyson in #807 * fix: Fix ownership of ClusterAutoscaler resources by @jimmidyson in #810 ### Other Changes * ci: Run e2e jobs only if unit-test, lint-*, and pre-commit jobs pass by @dlipovetsky in #796 * ci: Enable verbose output for e2e tests by @dlipovetsky in #797 * test: Verify ServiceLoadBalancer in e2e Docker and Nutanix tests by @dlipovetsky in #788 * refactor: Use CAPI conditions check where possible by @dlipovetsky in #789 * test(e2e): Use parallel tests for providers other than Docker by @jimmidyson in #787 ## New Contributors * @tuxtof made their first contribution in #805 **Full Changelog**: v0.12.1...v0.13.0 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Keep Docker using serial tests to not exhaust resources of the machine
that the Docker tests are running on. Other providers do not require so
many resources as they use cloud or external infrastructure for clusters.