ci: re-enable the nightly PreflightCheckRollback platform check - #38711
Merged
ggevay merged 1 commit intoSep 9, 2026
Merged
Conversation
The job was skipped on 2026-02-23 (MaterializeInc#35166) because of DB-85, where the 0dt preflight timed out waiting for the new environmentd to reach ReadyToPromote. MaterializeInc#35634 (2026-03-26) fixed the frontier that controller hydration compares against, and the sibling release-qualification scenario PreflightCheckContinue has been clean for 176 builds since 2026-04-12. Re-enabling the nightly job confirms that on the rollback path; DB-85 closes after a few green runs. 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.
The nightly job
checks-preflight-check-rollbackhas beenskip:-ped since 2026-02-23 (#35166) because of DB-85, where the 0dt preflight timed out waiting for the new environmentd to reachReadyToPromote.Evidence that the mechanism is fixed:
PreflightCheckContinue, which shares the scenario prefix and kept running, went from about 7 hits in 113 builds (February to April 2026) to 0 in 176 builds since 2026-04-12.This PR only removes the
skip:line so the rollback path gets the same confirmation on nightlies. DB-85 closes after a few green runs; if the timeout comes back, the job goes back to skipped and DB-85 gets the new build linked.Part of: DB-85
🤖 Generated with Claude Code