[Bug]: Test container leak

[Abacn]

What happened?

THere are many stale containers generated every day and staged in GCR

• For Java tests, there is a clean up script https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/scripts/cleanup_untagged_gcr_images.sh run after each postcommit. However it seems there is still leftovers
• For Pyhon&Go ARM tests, afaik it does not remove stale container after test run

Also, I am not sure the Python ARM test ever use the container for dataflow tests: it pushes image:

beam/sdks/python/test-suites/dataflow/common.gradle

Line 149 in a221f98

dependsOn ":sdks:python:container:py${pyversion}:docker"

but the later test is not referring the container pushed to GCR, and just uses beam-master one

Issue Priority

Priority: 3 (minor)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.