Skip to content

CI: Bump e2e timeout to 20'#4299

Open
pfcoperez wants to merge 1 commit into
mainfrom
ci/e2e/timeout-20min
Open

CI: Bump e2e timeout to 20'#4299
pfcoperez wants to merge 1 commit into
mainfrom
ci/e2e/timeout-20min

Conversation

@pfcoperez
Copy link
Copy Markdown
Contributor

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.

image

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.

@pfcoperez pfcoperez requested a review from a team as a code owner May 12, 2026 15:31
@claude
Copy link
Copy Markdown

claude Bot commented May 12, 2026

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@pfcoperez pfcoperez enabled auto-merge (squash) May 12, 2026 15:36
@codecov
Copy link
Copy Markdown

codecov Bot commented May 12, 2026

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@github-actions
Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: 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.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

❌ Test Failure

Analysis: 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.
Confidence: 0.9

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

❌ Test Failure

Analysis: 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.
Confidence: 0.85

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The e2e suite timed out at 900s; Test_PartitionBy fails deterministically across all 4 ClickHouse suites with a num vs (num) partition-expression mismatch likely caused by a ClickHouse upstream latest image version bump, and the resulting failure to drop an active replication slot cascades into Test_NullEngine timeouts — the triggering commit (MongoDB dynconf removal) is entirely unrelated to ClickHouse partitioning.
Confidence: 0.72

✅ Automatically retrying the workflow

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

❌ Test Failure

Analysis: 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.
Confidence: 0.92

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants