[repr types] Regression tests from reverted ColumnKnowledge#34905
Merged
mgree merged 1 commit intoMaterializeInc:mainfrom Feb 9, 2026
Merged
[repr types] Regression tests from reverted ColumnKnowledge#34905mgree merged 1 commit intoMaterializeInc:mainfrom
ColumnKnowledge#34905mgree merged 1 commit intoMaterializeInc:mainfrom
Conversation
mgree
added
C-bug
ggevay
approved these changes
Feb 9, 2026
mgree
added a commit
to mgree/materialize
that referenced
this pull request
Feb 9, 2026
…alizeInc#34905) MaterializeInc#34858 reverted MaterializeInc#34788, due to a variety of panics in a nightly run. This PR adds the failures from those panics to an SLT file, for regression testing in a rewrite of the original PR. ### Motivation * This PR introduces regression tests for a recognized bug. MaterializeInc/database-issues#10045 MaterializeInc/database-issues#10046 MaterializeInc/database-issues#10052
def-
added a commit
to def-/materialize
that referenced
this pull request
Feb 10, 2026
Introduced by MaterializeInc#34905 Seen in https://buildkite.com/materialize/nightly/builds/15083 Bail:test/sqllogictest/github-10045-10046-10052.slt:47 PlanFailure:test/sqllogictest/github-10045-10046-10052.slt:47: db error: ERROR: log source reads must target a replica DETAIL: The query references the following log sources: mz_compute_frontiers_per_worker HINT: Use `SET cluster_replica = <replica-name>` to target a specific replica in the active cluster. Note that subsequent queries will only be answered by the selected replica, which might reduce availability. To undo the replica selection, use `RESET cluster_replica`.
5 tasks
def-
added a commit
that referenced
this pull request
Feb 10, 2026
Introduced by #34905 Seen in https://buildkite.com/materialize/nightly/builds/15083 Bail:test/sqllogictest/github-10045-10046-10052.slt:47 PlanFailure:test/sqllogictest/github-10045-10046-10052.slt:47: db error: ERROR: log source reads must target a replica DETAIL: The query references the following log sources: mz_compute_frontiers_per_worker HINT: Use `SET cluster_replica = <replica-name>` to target a specific replica in the active cluster. Note that subsequent queries will only be answered by the selected replica, which might reduce availability. To undo the replica selection, use `RESET cluster_replica`. Test run: https://buildkite.com/materialize/nightly/builds/15084 ### Checklist - [ ] This PR has adequate test coverage / QA involvement has been duly considered. ([trigger-ci for additional test/nightly runs](https://trigger-ci.dev.materialize.com/)) - [ ] This PR has an associated up-to-date [design doc](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/README.md), is a design doc ([template](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/00000000_template.md)), or is sufficiently small to not require a design. <!-- Reference the design in the description. --> - [ ] If this PR evolves [an existing `$T ⇔ Proto$T` mapping](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/command-and-response-binary-encoding.md) (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](MaterializeInc/cloud#5021)). <!-- Ask in #team-cloud on Slack if you need help preparing the cloud PR. --> - [ ] If this PR includes major [user-facing behavior changes](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/guide-changes.md#what-changes-require-a-release-note), I have pinged the relevant PM to schedule a changelog post.
mgree
added a commit
that referenced
this pull request
Feb 13, 2026
This PR combines two bugfixes to give the best fix, allowing for multireplica tests. ### Motivation #34966 fixes an SLT test from #34905 that broke in nightly when run with multiple replicas. The fix there is better than the fix I put in #34958, which forces the test to only run in single replica mode. ### Description Takes the `singlereplica_` out of the name, so we'll actually run multi-replica tests. ### Verification Running appropriate 4-replica slt tests from nightly.
patrickwwbutler
pushed a commit
to patrickwwbutler/materialize
that referenced
this pull request
Feb 19, 2026
…alizeInc#34905) MaterializeInc#34858 reverted MaterializeInc#34788, due to a variety of panics in a nightly run. This PR adds the failures from those panics to an SLT file, for regression testing in a rewrite of the original PR. ### Motivation * This PR introduces regression tests for a recognized bug. MaterializeInc/database-issues#10045 MaterializeInc/database-issues#10046 MaterializeInc/database-issues#10052
patrickwwbutler
pushed a commit
to patrickwwbutler/materialize
that referenced
this pull request
Feb 19, 2026
…alizeInc#34905) MaterializeInc#34858 reverted MaterializeInc#34788, due to a variety of panics in a nightly run. This PR adds the failures from those panics to an SLT file, for regression testing in a rewrite of the original PR. ### Motivation * This PR introduces regression tests for a recognized bug. MaterializeInc/database-issues#10045 MaterializeInc/database-issues#10046 MaterializeInc/database-issues#10052
patrickwwbutler
pushed a commit
to patrickwwbutler/materialize
that referenced
this pull request
Feb 19, 2026
…c#34966) Introduced by MaterializeInc#34905 Seen in https://buildkite.com/materialize/nightly/builds/15083 Bail:test/sqllogictest/github-10045-10046-10052.slt:47 PlanFailure:test/sqllogictest/github-10045-10046-10052.slt:47: db error: ERROR: log source reads must target a replica DETAIL: The query references the following log sources: mz_compute_frontiers_per_worker HINT: Use `SET cluster_replica = <replica-name>` to target a specific replica in the active cluster. Note that subsequent queries will only be answered by the selected replica, which might reduce availability. To undo the replica selection, use `RESET cluster_replica`. Test run: https://buildkite.com/materialize/nightly/builds/15084 ### Checklist - [ ] This PR has adequate test coverage / QA involvement has been duly considered. ([trigger-ci for additional test/nightly runs](https://trigger-ci.dev.materialize.com/)) - [ ] This PR has an associated up-to-date [design doc](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/README.md), is a design doc ([template](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/00000000_template.md)), or is sufficiently small to not require a design. <!-- Reference the design in the description. --> - [ ] If this PR evolves [an existing `$T ⇔ Proto$T` mapping](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/command-and-response-binary-encoding.md) (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](MaterializeInc/cloud#5021)). <!-- Ask in #team-cloud on Slack if you need help preparing the cloud PR. --> - [ ] If this PR includes major [user-facing behavior changes](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/guide-changes.md#what-changes-require-a-release-note), I have pinged the relevant PM to schedule a changelog post.
patrickwwbutler
pushed a commit
to patrickwwbutler/materialize
that referenced
this pull request
Feb 19, 2026
…nc#34991) This PR combines two bugfixes to give the best fix, allowing for multireplica tests. ### Motivation MaterializeInc#34966 fixes an SLT test from MaterializeInc#34905 that broke in nightly when run with multiple replicas. The fix there is better than the fix I put in MaterializeInc#34958, which forces the test to only run in single replica mode. ### Description Takes the `singlereplica_` out of the name, so we'll actually run multi-replica tests. ### Verification Running appropriate 4-replica slt tests from nightly.
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.
#34858 reverted #34788, due to a variety of panics in a nightly run.
This PR adds the failures from those panics to an SLT file, for regression testing in a rewrite of the original PR.
Motivation
https://github.com/MaterializeInc/database-issues/issues/10045
https://github.com/MaterializeInc/database-issues/issues/10046
https://github.com/MaterializeInc/database-issues/issues/10052
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.