Antalya 26.8: Fix stale assertion in test_create_table_engine_backend_mismatch_rejected(Glue) by subkanthi · Pull Request #2869 · Altinity/ClickHouse · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Antalya 26.8: Fix stale assertion in test_create_table_engine_backend_mismatch_rejected(Glue) - #2869
subkanthi
changed the title
Fix stale assertion in test_create_table_engine_backend_mismatch_reje…
Antalya 26.8: Fix stale assertion in test_create_table_engine_backend_mismatch_rejected
Nov 16, 2026
subkanthi
changed the title
Antalya 26.8: Fix stale assertion in test_create_table_engine_backend_mismatch_rejected
Antalya 26.8: Fix stale assertion in test_create_table_engine_backend_mismatch_rejected(Glue)
Nov 16, 2026
Verdict: 1 failing check (Swarms regression). This PR did not cause it: the same failure shows up on other antalya-26.8 PRs. No fix is needed in this PR.
Next step: none for this PR. The Swarms failures (cluster discovery with a wrong cluster name, swarm node restart, cpu overload) are a problem on antalya-26.8 itself or in the regression suite, and should be tracked separately from this PR.
The edited test itself
The changed test ran in Integration tests (amd_asan_ubsan, db disk, old analyzer, 1/8) and passed:
So the new assertion (Table setting \disk` differs from its value in this DataLakeCatalog … would be lost`) matches what the server on this branch returns.
Note: most other jobs show SKIPPED. That's because of this PR's CI/CD options (e.g. Aarch64 excluded) and test-only job selection, not because they failed.
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
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.
Fix assertion error in tests/integration/test_database_glue/test.py
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix assertion error in tests/integration/test_database_glue/test.py
CI/CD Options
Exclude tests:
Regression jobs to run: