Repository navigation
Conversation
The lanes are steps of one job, so a failed lane skipped every later one and its result stayed unknown until a re-run: a flake in the gVisor lane hid the micro-VM lane on the same head. Every lane now runs once the setup before it succeeded, unless the run is cancelled, and reports its own outcome. The job and its name are unchanged. Signed-off-by: Timo Derstappen <teemow@gmail.com>
teemow
added a commit
to giantswarm/substrate
that referenced
this pull request
Oct 13, 2026
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>
The failure dump printed each ate-system pod's current logs only. When a container restarted during the suite (an OOM kill, a crash), the dump showed the new run and nothing of the run that ended, so the failures the restart caused carried no cause. Print every restarted container's termination state, its previous log, and the Warning events. Signed-off-by: QuentinBisson <quentin@giantswarm.io>
QuentinBisson
added a commit
to giantswarm/substrate
that referenced
this pull request
Oct 23, 2026
* docs(fork): T16 upstream state as of 2026-10-23 kagent-dev#71 carries the restarted-container dump as its second commit; the Helm version pin is kagent-dev#96; the helm-verify checkout bump stays fork-only. Signed-off-by: QuentinBisson <quentin@giantswarm.io> * docs(fork): kagent-dev#96 is ready for review Signed-off-by: QuentinBisson <quentin@giantswarm.io> --------- Signed-off-by: QuentinBisson <quentin@giantswarm.io>
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.
Problem
The lanes of
helm-e2eare steps of one job, so a failed lane skips every later one: a flake in the gVisor lane hides the micro-VM lane's result on the same head until a re-run, and a lane that is red cannot be told from one that never ran.Change
Every
Run E2E tests (…)step runs once the setup before it succeeded (steps.lanes-ready.outcome == 'success') unless the run is cancelled, and reports its own outcome. The job, its name and its steps' order are unchanged;Require every lane to have run testsstill runs always.Written by an agent on behalf of the Giant Swarm team.