Skip to content

Commit

Permalink
ci: Ignore new 0dt warning
Browse files Browse the repository at this point in the history
> platform-checks-mz_2-1              | environmentd: 2025-02-10T15:49:48.328178Z  WARN mz_environmentd::deployment::preflight: halting process: there have been DDL that we need to react to; rebooting in read-only mode

Seen in https://buildkite.com/materialize/nightly/builds/11099

This was part of MaterializeInc#31293, but somehow
got lost in main after merge
  • Loading branch information
def- committed Feb 10, 2025
1 parent 109406c commit 0d2bba4
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions misc/python/materialize/cli/ci_annotate_errors.py
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,7 @@
| \ ANOM_ABEND\ .*\ exe="/usr/bin/qemu
# This can happen in "K8s recovery: envd on failing node", but the test still succeeds, old environmentd will just be crashed, see database-issues#8749
| \[pod/environmentd-0/environmentd\]\ .*\ (unable\ to\ confirm\ leadership|fenced\ out\ old\ deployment;\ rebooting\ as\ leader|this\ deployment\ has\ been\ fenced\ out)
| halting\ process:\ there\ have\ been\ DDL\ that\ we\ need\ to\ react\ to;\ rebooting\ in\ read-only\ mode
)
""",
re.VERBOSE | re.MULTILINE,
Expand Down

0 comments on commit 0d2bba4

Please sign in to comment.