From 389aa97b400f921cedfdea48db6c178c550575b8 Mon Sep 17 00:00:00 2001 From: Gabor Gevay Date: Tue, 8 Sep 2026 12:08:52 +0200 Subject: [PATCH] ci: re-enable the nightly PreflightCheckRollback platform check The job was skipped on 2026-02-23 (#35166) because of DB-85, where the 0dt preflight timed out waiting for the new environmentd to reach ReadyToPromote. #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 --- ci/nightly/pipeline.template.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/ci/nightly/pipeline.template.yml b/ci/nightly/pipeline.template.yml index 3c418f9e46c13..538845a49e049 100644 --- a/ci/nightly/pipeline.template.yml +++ b/ci/nightly/pipeline.template.yml @@ -1278,7 +1278,6 @@ steps: - ./ci/plugins/mzcompose: composition: platform-checks args: [--scenario=PreflightCheckRollback, "--seed=$BUILDKITE_JOB_ID"] - skip: "flaky due to https://linear.app/materializeinc/issue/DB-85" - id: checks-0dt-restart-entire-mz-forced-migrations topics: [0dt-migration, copy-to-s3, debezium, iceberg, kafka, kafka-sink, mysql, postgres, sql-server, ssh-tunnel]