shunping opened a new issue, #37137: URL: https://github.com/apache/beam/issues/37137
### What happened? The workflow https://github.com/apache/beam/actions/workflows/beam_Playground_CI_Nightly.yml has been failing since the release of Beam 2.70. Even though the PR #37134 from @derrickaw was merged in the master, the test workflow is always using the latest released beam to build the backend container. This also explains why it started to fail after 2.70 was released. https://github.com/apache/beam/blob/8cc26a4be1fc54810a0e59afe65a7fcc671ef3c3/.github/workflows/beam_Playground_CI_Nightly.yml#L86 Fortunately, the playground website is not affected at the moment, because it is running on a snapshot image created before the culprit PR #36853. <img width="2300" height="478" alt="Image" src="https://github.com/user-attachments/assets/44a34ecc-fc52-4e4a-9803-f7e1b8bab40c"; /> ### Issue Failure Failure: Test is flaky ### Issue Priority Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy) ### 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: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
