CI: Bump e2e timeout to 20'#4299
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
|
🔄 Flaky Test DetectedAnalysis: CI infrastructure failure: the "Install ClickHouse (latest)" step failed with exit code 1 while downloading the nightly ClickHouse binary from builds.clickhouse.com — no tests ran at all, and the equivalent job using a pinned stable ClickHouse version succeeded. ✅ Automatically retrying the workflow |
❌ Test FailureAnalysis: All four test suite variants of Test_PartitionBy fail deterministically with the same assertion mismatch (expected "num" but got "(num)" for the ClickHouse partition key), and Test_NullEngine also fails consistently across all variants — indicating real bugs rather than flakiness. |
❌ Test FailureAnalysis: Test_PartitionBy fails deterministically across all 4 test suites with ClickHouse returning "(num)" instead of expected "num" for the partition key expression, indicating a real behavior change in the ClickHouse "latest" image rather than a flaky failure; Test_NullEngine also consistently times out waiting for records to replicate, likely caused by the same ClickHouse version bump. |
🔄 Flaky Test DetectedAnalysis: The e2e suite timed out at 900s; Test_PartitionBy fails deterministically across all 4 ClickHouse suites with a ✅ Automatically retrying the workflow |
❌ Test FailureAnalysis: Test_PartitionBy fails deterministically across all 4 test suite variants with a consistent assertion mismatch (expected "num", got "(num)" for ClickHouse partition_key), indicating a real bug — likely a ClickHouse version change that now wraps single-column partition keys in parentheses. |
Most of our successful CI e2e executions finish in the last 10'' before the 900'' (15') timeout.
This means that most of the runs are close to hit the timeout and the slightest delay leads to a failed e2e run which.
This process repeats several times until a run is fast enough per commit, per PR.
This PR bumps the timeout to 20' with the expectation of ending up with faster (no retries) and more predictable builds.