Skip to content

Speed up e2e test runtime by parallelizing specs and tightening polling#1001

Open
kelos-bot[bot] wants to merge 1 commit intomainfrom
kelos-task-997
Open

Speed up e2e test runtime by parallelizing specs and tightening polling#1001
kelos-bot[bot] wants to merge 1 commit intomainfrom
kelos-task-997

Conversation

@kelos-bot
Copy link
Copy Markdown

@kelos-bot kelos-bot Bot commented Apr 16, 2026

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:

  • Ginkgo runs specs serially
  • WaitForJobCompletion / WaitForDeploymentAvailable / WaitForCronJobCreated and TaskSpawner eventual checks poll every 10s, so a Task that finishes in 1s is still observed ~10s later

This PR:

  • Enables Ginkgo parallel execution via -p in the test-e2e target. Each spec already creates its own namespace via framework.NewFramework, so parallelism is safe.
  • Drops the long 10s poll intervals to 2s in framework waits and TaskSpawner specs. Polling a single Job/Deployment/CronJob every 2s is cheap and lets short jobs be observed much sooner.

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?

NONE

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.

  • Refactors
    • Enable Ginkgo parallel execution via -p in the test-e2e Makefile target; safe because each spec runs in its own namespace.
    • Reduce polling from 10s to 2s in WaitForJobCompletion, WaitForDeploymentAvailable, WaitForCronJobCreated, and TaskSpawner tests.

Written for commit e9a7fd5. Summary will update on new commits.

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>
@github-actions github-actions Bot added needs-triage kind/cleanup needs-kind Indicates an issue or PR lacks a kind/* label needs-priority needs-actor release-note-none and removed needs-kind Indicates an issue or PR lacks a kind/* label labels Apr 16, 2026
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

reduce e2e test duration

1 participant