[python] test_events: ignore Unavailable status events - #6799
Merged
Conversation
The runner records Unavailable whenever it momentarily cannot reach the pipeline, which reflects the cluster rather than the lifecycle under test. One such event, caused by a compiler-server outage that crash-looped the pipeline container, broke the exact-sequence assertion in cloud CI. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
gz
enabled auto-merge
August 4, 2026 05:17
mihaibudiu
approved these changes
Aug 4, 2026
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.
test_eventsasserts an exact status-event sequence, so it fails whenever the runnerhappens to record
Unavailable. That status means the runner momentarily could not reachthe pipeline, which reflects the cluster rather than the lifecycle under test.
Describe Manual Test Plan
Seen in CI a compiler-server outage crash-looped the pipeline container, the pod left service, its DNS
record was withdrawn, and the runner recorded one
Unavailableevent betweenInitializingand
Running:Replayed the 47 events that run recorded (from its support bundle) through the test's
mapping code:
Pausedtransition deletedThe last row matters: the filter drops only
Unavailable, and the test still catches alifecycle transition that goes missing.
Checklist
Breaking Changes?
None.