Skip to content

orchestratord test: rolling upgrade + introduce mz-debug #34214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

orchestratord test: rolling upgrade + introduce mz-debug #34214

wants to merge 1 commit into from
+39 −15

Conversation

@def-
Copy link
Contributor

@def- def- commented Nov 19, 2025 •
edited
Loading

Shouldn't be set, as noted by @alex-hunt-materialize
Test run: https://buildkite.com/materialize/nightly/builds/14124

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

alex-hunt-materialize
alex-hunt-materialize reviewed Nov 19, 2025
View reviewed changes
@def- def- force-pushed the pr-orchestratord-rolling-upgrade branch 3 times, most recently from 8304776 to b696e2d Compare November 20, 2025 11:37
@def- def- force-pushed the pr-orchestratord-rolling-upgrade branch from b696e2d to b42d451 Compare November 20, 2025 13:34
@alex-hunt-materialize alex-hunt-materialize mentioned this pull request Nov 20, 2025
Draft
5 tasks
@def- def- force-pushed the pr-orchestratord-rolling-upgrade branch from b42d451 to de0b470 Compare November 20, 2025 18:24
@def- def- requested a review from a team as a code owner November 20, 2025 18:24
@def- def- force-pushed the pr-orchestratord-rolling-upgrade branch from de0b470 to 37aff13 Compare November 20, 2025 18:25
@def- def- force-pushed the pr-orchestratord-rolling-upgrade branch from 37aff13 to 65bc9f3 Compare November 20, 2025 20:13
@def- def- changed the title orchestratord test: rolling upgrade orchestratord test: rolling upgrade + introduce mz-debug Nov 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bobbyiliev bobbyiliev bobbyiliev approved these changes

@alex-hunt-materialize alex-hunt-materialize alex-hunt-materialize approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@def- @bobbyiliev @alex-hunt-materialize