shehzaadn-vd edited a comment on pull request #12938: URL: https://github.com/apache/beam/pull/12938#issuecomment-752327457
> @kennknowles @ibzib any idea why org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement is showing up as failing even though it's excluded from running in beam/runners/portability/java/build.gradle > (excludeTestsMatching 'org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement') Did some digging around - 1) The task that's calling this failing test is :runners:direct-java:needsRunnerTests 2) Looking at the console output of the last successful build (#15306), (taking the listing of tasks on the left and doing some sort/uniq/diff on bash) this is the *only* task that actually gets called twice . Not sure if that's expected. Seems strange for a task to be executed twice. 3) In this build (#15307), we have the following tasks that are being called twice: :runners:direct-java:needsRunnerTests, :runners:flink:1.10:test, :runners:flink:1.11:test, :runners:samza:compileTestJava Could this failure be related to the same test being called more than once in the same runtime instance. Is it worth looking into removing this duplicate calling of tasks? Or maybe there's a simpler answer.... @kennknowles @ibzib thanks. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
