parallel-workload: ignore the RTR timeout in ExplainFilterPushdownAction - #38713
Merged
ggevay merged 1 commit intoSep 9, 2026
Conversation
SelectAction already treats "timed out before ingesting the source's visible frontier when real-time-recency query issued" as an ignorable error, because a session with real-time recency enabled can legitimately hit the RTR timeout. ExplainFilterPushdownAction issues EXPLAIN FILTER PUSHDOWN FOR SELECT ... on the same sessions and waits for the source the same way, but did not list the error, so the RTR timeout failed the whole workload (nightly 18001 and 18005, 2026-08-09; tracked under SS-303). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
aljoscha
approved these changes
Sep 9, 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
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.
SelectActionalready liststimed out before ingesting the source's visible frontier when real-time-recency query issuedas an ignorable error, because a session with real-time recency enabled can legitimately hit the RTR timeout.ExplainFilterPushdownActionrunsEXPLAIN FILTER PUSHDOWN FOR SELECT ...on the same sessions and waits for the source the same way, but did not list the error, so an RTR timeout there failed the whole workload: nightly 18001 and 18005 on 2026-08-09 (Parallel Correctness + cancel,Parallel Correctness + 0dt deploy).One-line addition to the action's
errors_to_ignore, mirroringSelectAction. Part of the CI-flake sweep under SS-303, which tracks the RTR timeout itself.🤖 Generated with Claude Code