CI Tests results ingestion: Follow-up improvements#4209
Conversation
❌ 2 Tests Failed:
View the top 3 failed test(s) by shortest run time
View the full list of 1 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
🔄 Flaky Test DetectedAnalysis: Both failures ( ✅ Automatically retrying the workflow |
…d field Co-authored-by: Ilia Demianenko <ilia.demianenko@clickhouse.com>
🔄 Flaky Test DetectedAnalysis: All three failures across different matrix jobs are infrastructure/timing issues (Temporal context deadline exceeded, PostgreSQL catalog connection terminated by admin command, async initial-load wait timeout), not deterministic test logic failures. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: Both failures are infrastructure/timing flakiness: one test lost its catalog DB connection mid-run (Postgres SQLSTATE 57P01 admin_shutdown), and another hit a snapshot status timeout — neither indicates a code regression. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: Both failures are transient infrastructure issues: one test failed with "context deadline exceeded" connecting to Temporal server, and the other timed out under heavy CI load (32 parallel e2e tests near the 900s limit). ✅ Automatically retrying the workflow |
Two improvements following up #4191