Update dockerfile dependencies#4170
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 |
🔄 Flaky Test DetectedAnalysis: Two e2e tests failed due to timeouts waiting on external services — one explicitly reports "UNEXPECTED TIMEOUT PubSub subscription waiting on message" and the other is a long-running ClickHouse types test that exceeded its time budget, both consistent with transient infrastructure flakiness rather than a code regression. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: Test at clickhouse_test.go:1163 fails due to a 1-microsecond time precision mismatch (18h41m9.872299s vs 18h41m9.872298s), a non-deterministic rounding issue indicative of a flaky test. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: The e2e integration test suite failed only in 1 of 3 matrix variants on a Renovate dependency-update PR (no logic changes), ran for 785s near the 900s timeout limit, suggesting a timing-sensitive flaky failure rather than a real bug. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: TestApiPg/TestTableAdditionWithoutInitialLoad failed due to a PostgreSQL SQLSTATE 57P01 (admin_shutdown) error — the catalog DB connection was terminated by an external administrative command, which is an intermittent infrastructure issue unrelated to test logic. ✅ Automatically retrying the workflow |
c6430bb to
988e18b
Compare
🔄 Flaky Test DetectedAnalysis: All three MySQL/MariaDB e2e matrix variants failed in a renovate Dockerfile-only PR, a pattern consistent with flaky integration tests rather than a real regression introduced by the change. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: Two E2E tests failed due to flaky timing issues: a snapshot status timeout in TestGenericBQ and a teardown race condition (active replication slot) in TestPeerFlowE2ETestSuitePG_CH_Cluster, both unrelated to the recent changestream commit. ✅ Automatically retrying the workflow |
988e18b to
ef3661a
Compare
🔄 Flaky Test DetectedAnalysis: Both failures occurred in test teardown (not assertions): one is a race condition where a PostgreSQL replication slot was still active when cleanup tried to drop it, and the other is a transient "conn closed" error during schema cleanup — both are infrastructure timing issues unrelated to the code changes. ✅ Automatically retrying the workflow |
ef3661a to
1475afc
Compare
1475afc to
b952033
Compare
This PR contains the following updates:
4a43a54→2780b5c2389ebf→c2a1f7bConfiguration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.