tchivs commented on PR #4530: URL: https://github.com/apache/flink-cdc/pull/4530#issuecomment-5630944851
Still red, but a different job and test this time: `Pipeline E2E Tests 2.x (4-Parallelism)` → `SchemaEvolvingTransformE2eITCase#testFineGrainedSchemaEvolution`, a `TimeoutException` waiting for an `AlterColumnTypeEvent` after 199s. Last run it was `MySqlToIcebergE2eITCase#testSyncWholeDatabase` plus a timeout in `TransformE2eITCase#testAssortedSchemaTransform`, on the 1.20.3 job. No TIME column in any of them. Otherwise 18/19 green, `testTemporalFunctions` and the postgres time-type cases included. Three runs, three different E2E timeouts — shall we treat that suite as pre-existing flake and track it separately? I can file the JIRA if you'd like. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
