spuru9 opened a new pull request, #307: URL: https://github.com/apache/flink-connector-kafka/pull/307
## What is the purpose of the change `SourceTopicIntegrityTest` intermittently times out on CI waiting for records in the sink topic (`TimeoutException: Timeout waiting for 100 records ... after PT2M`), observed across unrelated branches/PRs including a NOTICE-only change that touches no production code. See FLINK-40618 for the full analysis. Root cause: the test is a heavyweight integration test — it starts a Testcontainers Kafka broker and a 3-TaskManager MiniCluster and drives savepoint/restore — but its `*Test` suffix routed it into the unit-test surefire execution (`forkCount=4`, 1GB heap). Up to four such forks run in parallel, so multiple Testcontainers-Kafka + MiniCluster JVMs contend for Docker/CPU/IO on the runner, and the source→sink round trip can exceed the 2-minute wait. ## Brief change log - Rename `SourceTopicIntegrityTest` → `SourceTopicIntegrityITCase` so it is picked up by the integration-test execution (`forkCount=2`, 2GB heap, `reuseForks=false`) instead of the 4-way-parallel unit-test execution. - This matches the heavyweight siblings in the same package (`KafkaSourceITCase`, `KafkaSourceMigrationITCase`), which already use the same `KafkaSourceTestEnv` + `MiniClusterExtension` machinery and the `*ITCase` suffix. No test logic changes. ## Verifying this change - `mvn -pl flink-connector-kafka -am test-compile` passes. - CI should now run the test in the integration-test phase with reduced fork parallelism. - This reduces the resource contention behind the timeout; confirming the flakiness is gone requires observing it stay green across CI runs. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): **no** - The public API: **no** - The serializers: **no** - The runtime per-record code paths: **no** - Anything that affects deployment or recovery: **no** - The S3 file system connector: **no** ## Documentation - Does this pull request introduce a new feature? **no** -- 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]
