slachiewicz commented on PR #289:
URL: 
https://github.com/apache/flink-connector-kafka/pull/289#issuecomment-5479857164

   The previous CI run (`compile_and_test (17)`) hit a 50-minute timeout due to 
an intermittent hang in `SourceTestSuiteBase.testIdleReader`:
   
   ```text
   at 
org.apache.flink.streaming.api.operators.collect.CollectResultIterator.hasNext(CollectResultIterator.java:98)
   at 
org.apache.flink.connector.testframe.utils.CollectIteratorAssert.compareWithExactlyOnceSemantic(CollectIteratorAssert.java:130)
   at 
org.apache.flink.connector.testframe.utils.CollectIteratorAssert.matchesRecordsFromSource(CollectIteratorAssert.java:85)
   at 
org.apache.flink.connector.testframe.testsuites.SourceTestSuiteBase.checkResultWithSemantic(SourceTestSuiteBase.java:749)
   at 
org.apache.flink.connector.testframe.testsuites.SourceTestSuiteBase.testIdleReader(SourceTestSuiteBase.java:526)
   ```
   
   This is the known idle-reader hang race (where `no-more-splits` arrives 
before the metadata update) addressed in #291 
([FLINK-40362](https://issues.apache.org/jira/browse/FLINK-40362)). The failure 
is unrelated to the `ReaderRecoveryGate` refactoring in this PR.
   
   Re-pushed commit to trigger a clean CI run.


-- 
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]

Reply via email to