Conversation
❌ Test FailureAnalysis: Test_PartitionBy fails deterministically across all 4 test suites with a consistent assertion mismatch (expected partition key "num" but got "(num)"), indicating a real behavioral change — likely a newer ClickHouse version now wraps PARTITION BY expressions in parentheses. |
❌ Test FailureAnalysis: Test_CDC_V2_Protocol deterministically times out (200s) across all matrix jobs with other.NumRecords stuck at 1 instead of 2, indicating a real replication bug likely related to the ClickHouse ORDER BY/PARTITION BY change only partially fixed in the previous commit. |
🔄 Flaky Test DetectedAnalysis: Test_CDC_V2_Protocol times out at ~200s across all three matrix variants (199.33s–200.26s), indicating it's hitting an internal deadline rather than a real assertion failure, causing the overall e2e suite to exhaust the 900s timeout. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: All failures are timeout errors ("UNEXPECTED TIMEOUT waiting on initial", "UNEXPECTED TIMEOUT v2 single insert", "context deadline exceeded" on Temporal) across all three CI matrix jobs, indicating overloaded CI runners rather than a code regression. ✅ Automatically retrying the workflow |
❌ Test FailureAnalysis: Test_CDC_V2_Protocol fails deterministically across all 3 matrix configurations (~200s each), consistent with a real regression likely introduced by the recent ClickHouse PARTITION BY/ORDER BY change rather than a flaky environment issue. |
🔄 Flaky Test DetectedAnalysis: The e2e test suite for the maria/8.0 matrix job hit the hard 900-second timeout and was killed mid-run, with no assertion failures, indicating infrastructure slowness or a stuck test rather than a code regression. ✅ Automatically retrying the workflow |
❌ Test FailureAnalysis: Test_NullEngine deterministically fails in all 4 test suites (MySQL_CH, MySQL_CH_Cluster, PG_CH, PG_CH_Cluster) because the ClickHouse NullEngine table never accumulates records (other.NumRecords stays at 0 across every polling cycle), which is likely a real regression from the recent ClickHouse version behavior change (the prior commit already patched PARTITION BY/ORDER BY issues from the same upgrade). |
1 participant
No description provided.