raboof commented on issue #468: URL: https://github.com/apache/pekko-connectors/issues/468#issuecomment-2646170646
The problem is that, after the test finishes, there are still Streams components 'in flight', indicating some kind of leak in the stream teardown logic. The component that checks for these remaining running components helpfully products 'dot' graphs to diagnose what is waiting for what. Unfortunately these confuse me even more: it *seems* even 'headSink' is still waiting for input, even though that component should complete after producing its one and only value (and the test completing suggests that this has already happened). That could use additional research: is the component indeed still running, or is the dot output just confusing? However, while looking at this test again, I noticed that it is still using a topic that is also used in another test. While that doesn't really explain why the components still seem to be running after the test has completed, no good can come of it, so let's make sure those tests are independent with #981. Of course multiple tests sharing the same topic should still not lead to stream components getting left behind - but if making the tests more independent fixes the symptom of these flaky tests that's already a win in my book. -- 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: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
