test(platform): raise FT recovery waits from 90s to 300s - #6864
Merged
Conversation
A force-stop/start cycle can reschedule the pipeline pod onto another Kubernetes node, forcing its storage volume to detach and reattach. Under attach/detach contention the reattach alone can exceed 90s, which intermittently timed out test_ft_input_replay_determinism even though replay determinism held (deployment_error stayed unset through every cycle). The determinism assertion runs on every 0.5s poll, so the longer wait adds infrastructure headroom without weakening the regression check. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
mihaibudiu
approved these changes
Aug 14, 2026
mihaibudiu
left a comment
Contributor
There was a problem hiding this comment.
I hope they don't charge for this
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
2 participants
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.
A force-stop/start cycle can reschedule the pipeline pod onto another Kubernetes node, forcing its storage volume to detach and reattach. Under attach/detach contention the reattach alone can exceed 90s, which intermittently timed out
test_ft_input_replay_determinismeven though replay determinism held:deployment_errorstayed unset through every cycle, and the pod events showed a 2m35s volume-attach gap on the failing cycle.The determinism assertion runs on every 0.5s poll, so the longer wait adds infrastructure headroom without weakening the regression check. Normal cycles recover in seconds; only outlier cycles wait longer.