Skip to content

tests: Increase sleep in distinct_arrangements_mz_catalog_server.slt#35906

Merged
ggevay merged 1 commit intoMaterializeInc:mainfrom
ggevay:fix-distinct_arrangements_mz_catalog_server.slt
Apr 8, 2026
Merged

tests: Increase sleep in distinct_arrangements_mz_catalog_server.slt#35906
ggevay merged 1 commit intoMaterializeInc:mainfrom
ggevay:fix-distinct_arrangements_mz_catalog_server.slt

Conversation

@ggevay
Copy link
Copy Markdown
Contributor

@ggevay ggevay commented Apr 8, 2026

@ggevay ggevay added the T-testing Theme: tests or test infrastructure label Apr 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

  • Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
  • Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
  • Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • 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).

@ggevay ggevay marked this pull request as draft April 8, 2026 10:04
@ggevay ggevay force-pushed the fix-distinct_arrangements_mz_catalog_server.slt branch from 4ce9fbf to 4cb889c Compare April 8, 2026 10:07
@ggevay ggevay marked this pull request as ready for review April 8, 2026 10:12
@ggevay ggevay merged commit 4c1374a into MaterializeInc:main Apr 8, 2026
11 checks passed
ggevay added a commit that referenced this pull request Apr 11, 2026
…ery succeeded (#35908)

When we do `--auto-index-selects`, if the normal query fails, then the
error reporting gets quite complicated, and is currently buggy: We
return `InconsistentViewOutcome` when the normal query fails but the
view would fall under `INCONSISTENT_VIEW_OUTCOME_WARNING_REGEXPS`,
making the error msg quite misleading. [Slack
thread.](https://materializeinc.slack.com/archives/C01LKF361MZ/p1775637116095469?thread_ts=1775634600.931979&cid=C01LKF361MZ)

So, this PR simplifies `--auto-index-selects`, by making it try the view
only if the normal query succeeded. The rationale is that if the normal
query failed, then we don't want to involve the whole complicated
`--auto-index-selects` flow.

This also allowed simplifying some more code.

(Test run from before
#35906 was merged to
main, showing the new error:
https://buildkite.com/materialize/test/builds/120200#019d6d16-44c4-4480-a7f3-1b6edaf8b084
)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-testing Theme: tests or test infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants