See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/385/display/redirect?page=changes>
Changes: [noreply] Add typescript documentation to the programing guide. (#22137) [noreply] [Website] Update minimum required Go version for sdk development ------------------------------------------ [...truncated 47.97 KB...] > Task :sdks:java:container:goBuild /home/jenkins/go/bin/go1.18.1 build -o ./build/target/linux_amd64/boot boot.go boot_test.go > Task :sdks:java:container:java11:copySdkHarnessLauncher Execution optimizations have been disabled for task ':sdks:java:container:java11:copySdkHarnessLauncher' to ensure correctness due to the following reasons: - Gradle detected a problem with the following location: '<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src/sdks/java/container/build/target'.> Reason: Task ':sdks:java:container:java11:copySdkHarnessLauncher' uses this output of task ':sdks:java:container:downloadCloudProfilerAgent' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src/sdks/java/container/build/target'.> Reason: Task ':sdks:java:container:java11:copySdkHarnessLauncher' uses this output of task ':sdks:java:container:pullLicenses' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4/userguide/validation_problems.html#implicit_dependency for more details about this problem. > Task :release:go-licenses:java:createLicenses > Task :sdks:java:container:java11:copyGolangLicenses > Task :sdks:java:container:java11:dockerPrepare > Task :sdks:java:container:java11:docker > Task :runners:google-cloud-dataflow-java:buildAndPushDockerJavaContainer WARNING: `gcloud docker` will not be supported for Docker client versions above 18.03. As an alternative, use `gcloud auth configure-docker` to configure `docker` to use `gcloud` as a credential helper, then use `docker` as you would for non-GCR registries, e.g. `docker pull gcr.io/project-id/my-image`. Add `--verbosity=error` to silence this warning: `gcloud docker --verbosity=error -- pull gcr.io/project-id/my-image`. See: https://cloud.google.com/container-registry/docs/support/deprecation-notices#gcloud-docker The push refers to repository [us.gcr.io/apache-beam-testing/java-postcommit-it/java] e798b53a104b: Preparing 39fa68614b49: Preparing 51a6189957ac: Preparing 1edcfdab0da3: Preparing f05e5f716ff9: Preparing 600561ebeb25: Preparing 8d99532776fb: Preparing c24378aee6a1: Preparing 79c18ba1229d: Preparing 81b4a0041910: Preparing b80e87db9c63: Preparing 376c5cea7918: Preparing b615784d4259: Preparing 351a8d7eb0b5: Preparing 4098b1d8f15b: Preparing 7e145627a1fb: Preparing 6812ae0d9f23: Preparing 369123a7ed65: Preparing 5afd661c6106: Preparing 66183893ba24: Preparing 6840c8ff46bd: Preparing 97d5fec864d8: Preparing c24378aee6a1: Waiting 7e145627a1fb: Waiting 600561ebeb25: Waiting 6812ae0d9f23: Waiting 8d99532776fb: Waiting b615784d4259: Waiting 369123a7ed65: Waiting 79c18ba1229d: Waiting 351a8d7eb0b5: Waiting 5afd661c6106: Waiting 4098b1d8f15b: Waiting 81b4a0041910: Waiting b80e87db9c63: Waiting 97d5fec864d8: Waiting 66183893ba24: Waiting 6840c8ff46bd: Waiting f05e5f716ff9: Pushed 1edcfdab0da3: Pushed 39fa68614b49: Pushed 51a6189957ac: Pushed e798b53a104b: Pushed 8d99532776fb: Pushed c24378aee6a1: Pushed 600561ebeb25: Pushed 81b4a0041910: Pushed 376c5cea7918: Pushed b80e87db9c63: Pushed 7e145627a1fb: Layer already exists 6812ae0d9f23: Layer already exists 79c18ba1229d: Pushed 369123a7ed65: Layer already exists 5afd661c6106: Layer already exists 66183893ba24: Layer already exists 6840c8ff46bd: Layer already exists 97d5fec864d8: Layer already exists 351a8d7eb0b5: Pushed 4098b1d8f15b: Pushed b615784d4259: Pushed 20220710124127: digest: sha256:ef4d8c6929b81a0c14e82c6e6f0e68659b0ff7f93732b4a70b7dff262068f3fe size: 4935 > Task :sdks:java:testing:load-tests:run Jul 10, 2022 12:42:35 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create INFO: No stagingLocation provided, falling back to gcpTempLocation Jul 10, 2022 12:42:35 PM org.apache.beam.runners.dataflow.DataflowRunner fromOptions INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from the classpath: will stage 222 files. Enable logging at DEBUG level to see which files will be staged. Jul 10, 2022 12:42:36 PM org.apache.beam.sdk.Pipeline validate WARNING: The following transforms do not have stable unique names: ParDo(TimeMonitor) Jul 10, 2022 12:42:36 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Executing pipeline on the Dataflow Service, which will have billing implications related to Google Compute Engine usage and other Google Cloud Services. Jul 10, 2022 12:42:38 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location to prepare for execution. Jul 10, 2022 12:42:39 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 0 seconds Jul 10, 2022 12:42:39 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/ Jul 10, 2022 12:42:39 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage INFO: Uploading <112554 bytes, hash 31934a3f408e5d36507741d42521098134bffcd9816b50cdabbd0c5892804262> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-MZNKP0COXTZQd0HUJSEJgTS__NmBa1DNq70MWJKAQmI.pb Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input as step s1 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor) as step s2 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(ByteMonitor) as step s3 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 0 as step s4 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 1 as step s5 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 2 as step s6 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 3 as step s7 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 4 as step s8 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 5 as step s9 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 6 as step s10 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 7 as step s11 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 8 as step s12 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 9 as step s13 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor)2 as step s14 Jul 10, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Dataflow SDK version: 2.41.0-SNAPSHOT Jul 10, 2022 12:42:42 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: To access the Dataflow monitoring console, please navigate to https://console.cloud.google.com/dataflow/jobs/us-central1/2022-07-10_05_42_41-16620594327985251589?project=apache-beam-testing Jul 10, 2022 12:42:42 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Submitted job: 2022-07-10_05_42_41-16620594327985251589 Jul 10, 2022 12:42:42 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: To cancel the job using the 'gcloud' tool, run: > gcloud dataflow jobs --project=apache-beam-testing cancel > --region=us-central1 2022-07-10_05_42_41-16620594327985251589 Jul 10, 2022 12:42:45 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2022-07-10T12:42:44.534Z: The workflow name is not a valid Cloud Label. Labels applied to Cloud resources (such as GCE Instances) for monitoring will be labeled with this modified job name: load0tests0java110dataflow0v20batch0pardo01-jenkins-071012-o5nj. For the best monitoring experience, please name your job with a valid Cloud Label. For details, see: https://cloud.google.com/compute/docs/labeling-resources#restrictions Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:50.611Z: Worker configuration: e2-standard-2 in us-central1-b. Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.142Z: Expanding SplittableParDo operations into optimizable parts. Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.176Z: Expanding CollectionToSingleton operations into optimizable parts. Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.236Z: Expanding CoGroupByKey operations into optimizable parts. Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.272Z: Expanding GroupByKey operations into optimizable parts. Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.339Z: Fusing adjacent ParDo, Read, Write, and Flatten operations Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.365Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.401Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.434Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.468Z: Fusing consumer ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.503Z: Fusing consumer ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.523Z: Fusing consumer Step: 0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.553Z: Fusing consumer Step: 1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.586Z: Fusing consumer Step: 2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.620Z: Fusing consumer Step: 3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.663Z: Fusing consumer Step: 4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.689Z: Fusing consumer Step: 5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.719Z: Fusing consumer Step: 6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.800Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.828Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.857Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:51.883Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation) Jul 10, 2022 12:42:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:52.187Z: Executing operation Read input/Impulse+Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)+Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction+Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing Jul 10, 2022 12:42:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:42:52.264Z: Starting 5 ****s in us-central1-b... Jul 10, 2022 12:43:21 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:43:20.864Z: Your project already contains 100 Dataflow-created metric descriptors, so new user metrics of the form custom.googleapis.com/* will not be created. However, all user metrics are also available in the metric dataflow.googleapis.com/job/user_counter. If you rely on the custom metrics, you can delete old / unused metric descriptors. See https://developers.google.com/apis-explorer/#p/monitoring/v3/monitoring.projects.metricDescriptors.list and https://developers.google.com/apis-explorer/#p/monitoring/v3/monitoring.projects.metricDescriptors.delete Jul 10, 2022 12:43:28 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:43:28.268Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s). Jul 10, 2022 12:44:25 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:44:22.823Z: Workers have started successfully. Jul 10, 2022 12:44:37 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:44:37.427Z: Finished operation Read input/Impulse+Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)+Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction+Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing Jul 10, 2022 12:44:37 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:44:37.557Z: Executing operation Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step: 0/ParMultiDo(CounterOperation)+Step: 1/ParMultiDo(CounterOperation)+Step: 2/ParMultiDo(CounterOperation)+Step: 3/ParMultiDo(CounterOperation)+Step: 4/ParMultiDo(CounterOperation)+Step: 5/ParMultiDo(CounterOperation)+Step: 6/ParMultiDo(CounterOperation)+Step: 7/ParMultiDo(CounterOperation)+Step: 8/ParMultiDo(CounterOperation)+Step: 9/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) > Task :sdks:java:testing:load-tests:run FAILED The message received from the daemon indicates that the daemon has disappeared. Build request sent: Build{id=77cbfa48-45a2-46a8-b78a-d3709527ca78, currentDir=<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src}> Attempting to read last messages from the daemon log... Daemon pid: 3469472 log file: /home/jenkins/.gradle/daemon/7.4/daemon-3469472.out.log ----- Last 20 lines from daemon log file - daemon-3469472.out.log ----- Jul 10, 2022 12:44:37 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-10T12:44:37.557Z: Executing operation Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step: 0/ParMultiDo(CounterOperation)+Step: 1/ParMultiDo(CounterOperation)+Step: 2/ParMultiDo(CounterOperation)+Step: 3/ParMultiDo(CounterOperation)+Step: 4/ParMultiDo(CounterOperation)+Step: 5/ParMultiDo(CounterOperation)+Step: 6/ParMultiDo(CounterOperation)+Step: 7/ParMultiDo(CounterOperation)+Step: 8/ParMultiDo(CounterOperation)+Step: 9/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220710124127 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:ef4d8c6929b81a0c14e82c6e6f0e68659b0ff7f93732b4a70b7dff262068f3fe Remove shutdown hook failed Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) at java.lang.Runtime.removeShutdownHook(Runtime.java:239) at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:38) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) at org.gradle.process.internal.DefaultExecHandle.finished(DefaultExecHandle.java:356) at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:110) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ----- End of the daemon log ----- FAILURE: Build failed with an exception. * What went wrong: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. * Get more help at https://help.gradle.org > Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220710124127 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:ef4d8c6929b81a0c14e82c6e6f0e68659b0ff7f93732b4a70b7dff262068f3fe Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
