Speed up e2e test runtime by parallelizing specs and tightening polling#1001
Open
kelos-bot[bot] wants to merge 1 commit intomainfrom
Open
Speed up e2e test runtime by parallelizing specs and tightening polling#1001kelos-bot[bot] wants to merge 1 commit intomainfrom
kelos-bot[bot] wants to merge 1 commit intomainfrom
Conversation
Enable Ginkgo parallel execution with -p and reduce polling intervals from 10s to 2s in framework waits and TaskSpawner tests. Each spec already creates its own namespace via the framework, so parallel execution is safe. Most test durations were dominated by the 10s poll interval — dropping to 2s lets short-lived jobs finish earlier while still keeping polling cheap. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
E2E tests currently take ~5 minutes (291s in the last main run) because:
WaitForJobCompletion/WaitForDeploymentAvailable/WaitForCronJobCreatedand TaskSpawner eventual checks poll every 10s, so a Task that finishes in 1s is still observed ~10s laterThis PR:
-pin thetest-e2etarget. Each spec already creates its own namespace viaframework.NewFramework, so parallelism is safe.Combined, these should significantly reduce the e2e test duration.
Which issue(s) this PR is related to:
Fixes #997
Special notes for your reviewer:
No test behavior changes; only scheduling and poll cadence.
Does this PR introduce a user-facing change?
Summary by cubic
Speeds up e2e tests by running specs in parallel and tightening polling to cut idle wait time. Aligns with Linear #997 to reduce runtime without changing test behavior.
-pin thetest-e2eMakefile target; safe because each spec runs in its own namespace.WaitForJobCompletion,WaitForDeploymentAvailable,WaitForCronJobCreated, and TaskSpawner tests.Written for commit e9a7fd5. Summary will update on new commits.