ableegoldman opened a new pull request #11824: URL: https://github.com/apache/kafka/pull/11824
Seen a few of the new tests added [fail on PR builds](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-11812/3/testReport/org.apache.kafka.streams.integration/NamedTopologyIntegrationTest/Build___JDK_11_and_Scala_2_13___shouldRemoveOneNamedTopologyWhileAnotherContinuesProcessing/) lately with the classic ``` java.lang.AssertionError: Expected all streams instances in [org.apache.kafka.streams.processor.internals.namedtopology.KafkaStreamsNamedTopologyWrapper@7fb3e6b0] to be RUNNING within 30000 ms, but the following were not: {org.apache.kafka.streams.processor.internals.namedtopology.KafkaStreamsNamedTopologyWrapper@7fb3e6b0=ERROR} ``` Since Jenkins unfortunately truncates the logs before we even get to running this specific test (due to large kafka & Config logging, see #11823) so I can't say for sure that it's environmental vs an actual issue, but bumping up the timeout will help us rule this out if we continue to see failures. We already had some tests using the 30s timeout while others were bumped all the way up to 60s, I figured we should try out a default timeout of 45s and if we still see failures in specific tests we can go from there -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
