tvalentyn opened a new issue, #32492: URL: https://github.com/apache/beam/issues/32492
### What happened? There is evidence that Go-Using-Java XLang scenario might not we working well. Once we can prioritize this, we should fix and re-enable the following suites (which have been perma-red): * https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_GoUsingJava_Dataflow.yml * GoUsingJava scenarios in https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_Direct.yml , see: https://github.com/apache/beam/pull/32423 cc: @lostluck cc: @chamikaramj ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [X] Component: Java SDK - [X] 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 - [X] 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]
