Bring Windows integration test runtime down to less than half #6965
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.
Description
This changelist parallelises the Windows integration test specs by modifying the integration test runner to accept arbitrary arguments to be passed to the
ginkgo
binary, allowing the integration test GitHub workflow to pass the-p
and--procs
arguments to parallelise running the test specs. This has brought the total runtime of Windows integration tests down to ~55 minutes from ~2 hours and 30 minutes.The cluster version used in the tests has been updated to the latest EKS version 1.27, and as a result, one of the tests that uses the Docker runtime has been removed as it's no longer supported.
Checklist
README.md
, or theuserdocs
directory)area/nodegroup
) and kind (e.g.kind/improvement
)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 馃く