See 
<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/410/display/redirect?page=changes>

Changes:

[chamikaramj] Mention Java RunInference support in the Website

[noreply] Update run_inference_basic.ipynb

[noreply] Update CHANGE.md after 2.41.0 cut (#22577)

[noreply] Convert to BeamSchema type from ReadfromBQ (#17159)

[noreply] Fix deleteTimer in InMemoryTimerInternals and enable VR tests for


------------------------------------------
[...truncated 46.76 KB...]
github.com/apache/beam/sdks/v2/java/container,https://github.com/apache/beam/blob/sdks/v2.40.0/sdks/LICENSE,Apache-2.0
github.com/golang/protobuf,https://github.com/golang/protobuf/blob/v1.5.2/LICENSE,BSD-3-Clause
golang.org/x/net,https://cs.opensource.google/go/x/net/+/c690dde0:LICENSE,BSD-3-Clause
golang.org/x/sys,https://cs.opensource.google/go/x/sys/+/bc2c85ad:LICENSE,BSD-3-Clause
golang.org/x/text,https://cs.opensource.google/go/x/text/+/v0.3.7:LICENSE,BSD-3-Clause
google.golang.org/genproto/googleapis/rpc/status,https://github.com/googleapis/go-genproto/blob/e326c6e8e9c8/LICENSE,Apache-2.0
google.golang.org/grpc,https://github.com/grpc/grpc-go/blob/v1.47.0/LICENSE,Apache-2.0
google.golang.org/protobuf,https://github.com/protocolbuffers/protobuf-go/blob/v1.28.0/LICENSE,BSD-3-Clause
+ chmod -R a+w /output/licenses

> Task :sdks:java:container:java11:copyJavaThirdPartyLicenses

> 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]
4f7dfde85a4d: Preparing
a0e0b5e6ffc4: Preparing
1b5f5be4f55e: Preparing
3d603bbee5b5: Preparing
6858b4dc2e92: Preparing
9b4eda790228: Preparing
252e593e899a: Preparing
bb6e9a129195: Preparing
4033bad68f0c: Preparing
dda42e98cf64: Preparing
ad6a8896753d: Preparing
149238313158: Preparing
41bbbce4579c: Preparing
e54bff5417f0: Preparing
775d796d83dc: Preparing
7b7f3078e1db: Preparing
826c3ddbb29c: Preparing
b626401ef603: Preparing
9b55156abf26: Preparing
293d5db30c9f: Preparing
03127cdb479b: Preparing
9c742cd6c7a5: Preparing
e54bff5417f0: Waiting
9b55156abf26: Waiting
dda42e98cf64: Waiting
9b4eda790228: Waiting
293d5db30c9f: Waiting
ad6a8896753d: Waiting
252e593e899a: Waiting
03127cdb479b: Waiting
149238313158: Waiting
775d796d83dc: Waiting
41bbbce4579c: Waiting
9c742cd6c7a5: Waiting
b626401ef603: Waiting
3d603bbee5b5: Pushed
a0e0b5e6ffc4: Pushed
1b5f5be4f55e: Pushed
6858b4dc2e92: Pushed
4f7dfde85a4d: Pushed
bb6e9a129195: Pushed
252e593e899a: Pushed
dda42e98cf64: Pushed
9b4eda790228: Pushed
4033bad68f0c: Pushed
ad6a8896753d: Pushed
7b7f3078e1db: Layer already exists
826c3ddbb29c: Layer already exists
b626401ef603: Layer already exists
9b55156abf26: Layer already exists
293d5db30c9f: Layer already exists
03127cdb479b: Layer already exists
149238313158: Pushed
9c742cd6c7a5: Layer already exists
e54bff5417f0: Pushed
775d796d83dc: Pushed
41bbbce4579c: Pushed
20220804124128: digest: 
sha256:ae9e86fd6444798e6caf3aabaa15036a2b1cc3ecfefa852017fa36aba198e101 size: 
4935

> Task :sdks:java:testing:load-tests:run
Aug 04, 2022 12:42:36 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Aug 04, 2022 12:42:36 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.
Aug 04, 2022 12:42:37 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: 
ParDo(TimeMonitor)
Aug 04, 2022 12:42:37 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.
Aug 04, 2022 12:42:44 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Aug 04, 2022 12:42:45 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 1 
seconds
Aug 04, 2022 12:42:45 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Aug 04, 2022 12:42:45 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <112521 bytes, hash 
647cf1474dbdb9b915564c1944ec99cb34b7eac0cfb46feb20f69cdca013c6b0> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-ZHzxR029ubkVVkwZROyZyzS36sDPtG_rIPac3KATxrA.pb
Aug 04, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Aug 04, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Aug 04, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Aug 04, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 1 as step s5
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 2 as step s6
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 3 as step s7
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 4 as step s8
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 5 as step s9
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 6 as step s10
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 7 as step s11
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 8 as step s12
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 9 as step s13
Aug 04, 2022 12:42:47 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s14
Aug 04, 2022 12:42:47 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.42.0-SNAPSHOT
Aug 04, 2022 12:42:47 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-08-04_05_42_47-18275769220441744217?project=apache-beam-testing
Aug 04, 2022 12:42:47 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-08-04_05_42_47-18275769220441744217
Aug 04, 2022 12:42:47 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-08-04_05_42_47-18275769220441744217
Aug 04, 2022 12:42:58 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-08-04T12:42:55.652Z: 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-080412-75bq. 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
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:58.956Z: Worker configuration: e2-standard-2 in 
us-central1-a.
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.667Z: Expanding SplittableParDo operations into 
optimizable parts.
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.692Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.757Z: Expanding CoGroupByKey operations into 
optimizable parts.
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.786Z: Expanding GroupByKey operations into 
optimizable parts.
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.856Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.902Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.922Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.946Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:42:59.977Z: Fusing consumer 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.000Z: Fusing consumer 
ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.032Z: Fusing consumer Step: 
0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.059Z: Fusing consumer Step: 
1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.084Z: Fusing consumer Step: 
2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.103Z: Fusing consumer Step: 
3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.128Z: Fusing consumer Step: 
4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.149Z: Fusing consumer Step: 
5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.169Z: Fusing consumer Step: 
6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.191Z: Fusing consumer Step: 
7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.216Z: Fusing consumer Step: 
8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.238Z: Fusing consumer Step: 
9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.261Z: Fusing consumer 
ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 
9/ParMultiDo(CounterOperation)
Aug 04, 2022 12:43:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.601Z: 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
Aug 04, 2022 12:43:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:00.668Z: Starting 5 ****s in us-central1-a...
Aug 04, 2022 12:43:09 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:09.883Z: 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
Aug 04, 2022 12:43:37 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:36.900Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).

> 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=d7e80833-309a-4cc3-8b61-b0b9028a6f3a, 
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: 3921224
  log file: /home/jenkins/.gradle/daemon/7.4/daemon-3921224.out.log
----- Last  20 lines from daemon log file - daemon-3921224.out.log -----
Aug 04, 2022 12:43:09 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:09.883Z: 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
Aug 04, 2022 12:43:37 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-04T12:43:36.900Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Daemon vm is shutting down... The daemon has exited normally or was terminated 
in response to a user interrupt.
Remove shutdown hook failed
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.aborted(DefaultExecHandle.java:365)
        at 
org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108)
        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
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]

Reply via email to