The PostCommit XVR PythonUsingJavaSQL Dataflow job is flaky
The PostCommit XVR PythonUsingJavaSQL Dataflow is failing over 50% of the time Please visit https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_PythonUsingJavaSQL_Dataflow.yml?query=is%3Afailure+branch%3Amaster to see the logs.
See #30584 this is a infra issue and mitigated
Reopening since the workflow is still flaky
now it fails to build container image:
1: Task failed with an exception.
-----------
* Where:
Build file '/runner/_work/beam/beam/runners/google-cloud-dataflow-java/build.gradle' line: 293
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.4/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
* What went wrong:
Execution failed for task ':runners:google-cloud-dataflow-java:buildAndPushDockerJavaContainer'.
> Process 'command 'gcloud'' finished with non-zero exit value 1
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.
==============================================================================
2: Task failed with an exception.
-----------
* Where:
Build file '/runner/_work/beam/beam/runners/google-cloud-dataflow-java/build.gradle' line: 336
* What went wrong:
Execution failed for task ':runners:google-cloud-dataflow-java:buildAndPushDockerPythonContainer'.
> Process 'command 'gcloud'' finished with non-zero exit value 1
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.
==============================================================================
Seems due to #30866 updated gcloud in runner image
Reopening since the workflow is still flaky
Reopening since the workflow is still flaky
There is one test failing : SqlTransformTest.test_zetasql_generate_data likely due to #32902
Update: opened #33213 for fix
Job has been stable for 2 months. Closing as resolved.
Reopening since the workflow is still flaky
Fixed by https://github.com/apache/beam/pull/34439