Skip to content

ci(helm-e2e): run every lane whatever an earlier lane did - #366

Merged
teemow merged 2 commits into
giantswarmfrom
fork/helm-e2e-independent-lanes
Oct 13, 2026
Merged

teemow merged 2 commits into
giantswarmfrom
fork/helm-e2e-independent-lanes

Conversation

@teemow

@teemow teemow commented Oct 13, 2026

Copy link
Copy Markdown
Member

Problem

The lanes of helm-e2e are steps of one job, so a failed lane skips every later one; a flake in the gVisor lane hid the micro-VM lane on the same head (#365).

Change

Every Run E2E tests (…) step runs once the setup succeeded (unless the run is cancelled) and reports its own outcome. The job e2e-test keeps its name; the required checks (run-tests, govulncheck, fork-ledger) are untouched. Upstream: kagent-dev#71, ledger file in fork/.

Closes #365

A failed lane skipped every later lane of the one job, so a flake in the gVisor lane hid the micro-VM lane's result. Every lane now runs once the setup succeeded and reports its own outcome; the job name is unchanged. Carries kagent-dev#71.

Signed-off-by: Timo Derstappen <teemow@gmail.com>
@teemow
teemow requested a review from a team as a code owner October 13, 2026 00:30
Signed-off-by: Timo Derstappen <teemow@gmail.com>
@teemow
teemow merged commit d8b9392 into giantswarm Oct 13, 2026
17 checks passed
@teemow
teemow deleted the fork/helm-e2e-independent-lanes branch October 13, 2026 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

helm-e2e: a failed lane skips every later lane

1 participant