[DBI-829] Extended GTID e2e and UTs#4493
Conversation
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
❌ Test FailureAnalysis: The new test TestMySQLGetMasterGTIDSet deterministically fails only on the maria-pos matrix config (other 3 configs pass) because it wrongly expects an error from GetMasterGTIDSet on MariaDB in position mode, indicating an incorrect test assumption rather than a flaky failure. |
🔄 Flaky Test DetectedAnalysis: The unrelated Postgres test TestGenericPG/Test_Inheritance_Table_With_Dynamic_Setting timed out waiting for the snapshot to reach RUNNING status (61s) due to high-concurrency resource contention (statement timeouts in Postgres logs), while the other two matrix shards—including the PR's actual maria-gtid target—passed. ✅ Automatically retrying the workflow |
QA ValidationI intentionally left It did fail as expected. |
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
94a135d to
5117f08
Compare
ilidemi
left a comment
There was a problem hiding this comment.
I now realize where my previous confusion came from. 829 should've been split into two tasks, GTID parsing and adding newer Maria to CI. It's the newer Maria that unblocks other tasks, that are related to handling its features.
| db-version: [ | ||
| {pg: 16, mysql: 'mysql-gtid', mongo: '6.0', ch: 'lts'}, | ||
| {pg: 17, mysql: 'mysql-pos', mongo: '7.0', ch: 'stable'}, | ||
| {pg: 18, mysql: 'maria-pos', mongo: '8.0', ch: 'latest'}, |
There was a problem hiding this comment.
There's one more place with maria-pos (moved in #4452)
Used the occasion to refactor replication_mechanism_test into case values
dfc4d02 to
dbc708a
Compare
Follows: #4478
Closes: https://linear.app/clickhouse/issue/DBI-829