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 of the screen and doing some sort/uniq/diff on bash) this is being executed multiple times. Not sure if that's expected. Other such tasks are: :runners:google-cloud-dataflow-java:compileTestJava, :runners:google-cloud-dataflow-java:worker:compileJava, :runners:google-cloud-dataflow-java:worker:compileTestJava, :runners:google-cloud-dataflow-java:worker:legacy-worker:compileJava, :runners:google-cloud-dataflow-java:worker:legacy-worker:compileTestJava, :sdks:go:resolveBuildDependencies, :sdks:java:extensions:sql:compileTestJava. These others might be harmless. 3) In this build (#15307), we have a much larger number of tasks that are being executed multiple times.. 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.... Or, separately, should the excudeTestsMatching clauses that are in portabilility/build.gradle (as part of PR https://github.com/apache/beam/pull/11792) also be added to direct-java/build.gradle? @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]
