classify mysql client transient error#4197
Conversation
❌ 2 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
0754569 to
fe52dc9
Compare
🔄 Flaky Test DetectedAnalysis: The test failed due to a PostgreSQL catalog connection being forcibly terminated by an admin command (SQLSTATE 57P01 admin_shutdown), a transient infrastructure error unrelated to the test logic — all functional steps of the test completed successfully before this connection drop. ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: Three different e2e tests failed across different matrix configurations with timing-related errors (ClickHouse table-not-ready race, snapshot status timeout, schema teardown failure), all consistent with flaky distributed-system integration tests rather than a code regression. ✅ Automatically retrying the workflow |
Invalid sequence error is a known issue in the go-mysql-org client that needs to be classified. Previously fixed for cdc (#4197) but missing for snapshot during ExecuteSelectStreaming. Fixes: DBI-743
Retry transient auth error that can happen occasionally when creating a binlogSyncer:
MySQL client received package with sequence number
2when it expected3during auth handshake, then succeeds on retry. Suggest a bug in the auth handshake code in go-mysql-org client.We've seen similar issue in the past with
invalid sequence 4 != 5that also succeeded on retryFixes: DBI-414