Efrat19 commented on PR #288: URL: https://github.com/apache/flink-connector-kafka/pull/288#issuecomment-5385138131
> Added the measurements behind the 15-minute figure to the description. The motivation is the 50-minute job timeout: one hung test currently eats the whole budget and takes the rest of the suite with it, without ever producing a stack trace. > > For sizing, `KafkaSinkITCase` (the heaviest class here, 117 methods, 712s total) has a slowest single method of 33.7s, and that class costs ~700s in CI vs 712s locally — so the headroom is real on CI runners too. Sounds legit Would it make sense to create another ticket for tracking slow ITCases and see if we can refactor them? -- 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]
