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

Changes:

[noreply] Improve error message (#24843)

[noreply] Playground Example CI fix for 24807 (#24819)

[noreply] Bump github.com/tetratelabs/wazero from 1.0.0-pre.4 to 1.0.0-pre.7 in

[noreply] Fix beam_CleanUpGCPResources job (#24770)

[noreply] Set DELETE_BEFORE_DAY in accordance with release period (#24867)

[noreply] adding parameters flag to support schema based transforms (#24864)

[noreply] Fix SQLIO Performance Test (#24824)

[noreply] Reduce redundant Get API call when creating bq temp dataset (#24831)


------------------------------------------
[...truncated 169.25 KB...]
> Task :sdks:java:io:google-cloud-platform:jar UP-TO-DATE
> Task :sdks:java:testing:load-tests:compileJava UP-TO-DATE
> Task :sdks:java:testing:load-tests:classes UP-TO-DATE
> Task :sdks:java:testing:load-tests:jar UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:compileJava UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:classes UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:jar UP-TO-DATE

> Task :sdks:java:container:java17:copySdkHarnessLauncher
Execution optimizations have been disabled for task 
':sdks:java:container:java17: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_GBK_Dataflow_V2_Streaming_Java17/ws/src/sdks/java/container/build/target'.>
 Reason: Task ':sdks:java:container:java17: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.5.1/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_GBK_Dataflow_V2_Streaming_Java17/ws/src/sdks/java/container/build/target'.>
 Reason: Task ':sdks:java:container:java17: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.5.1/userguide/validation_problems.html#implicit_dependency
 for more details about this problem.

> Task :sdks:java:container:java17:copyDockerfileDependencies UP-TO-DATE
> Task :sdks:java:container:java17:dockerPrepare
> Task :sdks:java:container:java17: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]
86a5a51d9561: Preparing
f7ff7db84359: Preparing
04fde5dc96da: Preparing
0604eaad6336: Preparing
3a233c1a141e: Preparing
e6da697ffc09: Preparing
1bd16864a7a1: Preparing
74458ce4963b: Preparing
9634d722d1c4: Preparing
cdeea49bc8b2: Preparing
a41a48b2d0ed: Preparing
8616fa582141: Preparing
668a0b24b579: Preparing
f0de9a2c1453: Preparing
866db27bd042: Preparing
3bc383470c05: Preparing
e93827457889: Preparing
08fa02ce37eb: Preparing
a037458de4e0: Preparing
bafdbe68e4ae: Preparing
a13c519c6361: Preparing
668a0b24b579: Waiting
1bd16864a7a1: Waiting
f0de9a2c1453: Waiting
74458ce4963b: Waiting
a037458de4e0: Waiting
9634d722d1c4: Waiting
866db27bd042: Waiting
bafdbe68e4ae: Waiting
8616fa582141: Waiting
cdeea49bc8b2: Waiting
a13c519c6361: Waiting
3bc383470c05: Waiting
e6da697ffc09: Waiting
04fde5dc96da: Pushed
3a233c1a141e: Pushed
f7ff7db84359: Pushed
0604eaad6336: Pushed
86a5a51d9561: Pushed
1bd16864a7a1: Pushed
74458ce4963b: Pushed
cdeea49bc8b2: Pushed
8616fa582141: Pushed
9634d722d1c4: Pushed
a41a48b2d0ed: Pushed
3bc383470c05: Layer already exists
e93827457889: Layer already exists
08fa02ce37eb: Layer already exists
a037458de4e0: Layer already exists
bafdbe68e4ae: Layer already exists
a13c519c6361: Layer already exists
668a0b24b579: Pushed
f0de9a2c1453: Pushed
866db27bd042: Pushed
e6da697ffc09: Pushed
20230104142824: digest: 
sha256:7b2f24f25cbeb231431be1ec1864f7524185878de7150594c3fed51d908f3983 size: 
4728

> Task :sdks:java:testing:load-tests:run
Jan 04, 2023 2:28:52 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Jan 04, 2023 2:28:52 PM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from 
the classpath: will stage 232 files. Enable logging at DEBUG level to see which 
files will be staged.
Jan 04, 2023 2:28:53 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.
Jan 04, 2023 2:28:55 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 232 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Jan 04, 2023 2:28:55 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 232 files cached, 0 files newly uploaded in 0 
seconds
Jan 04, 2023 2:28:55 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Jan 04, 2023 2:28:55 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <101767 bytes, hash 
caac7dd383237af16e0d2e003cbc0e07134726c83276f80c151bd999c3132cea> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-yqx904MjevFuDS4APLwOBxNHJsgydvgMFRvZmcMTLOo.pb
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input/DataflowRunner.StreamingUnboundedRead.ReadWithIds as 
step s1
Jan 04, 2023 2:28:57 PM 
org.apache.beam.sdk.io.synthetic.SyntheticUnboundedSource split
INFO: Split into 20 bundles: [SyntheticUnboundedSource{startOffset=0, 
endOffset=1000}, SyntheticUnboundedSource{startOffset=1000, endOffset=2000}, 
SyntheticUnboundedSource{startOffset=2000, endOffset=3000}, 
SyntheticUnboundedSource{startOffset=3000, endOffset=4000}, 
SyntheticUnboundedSource{startOffset=4000, endOffset=5000}, 
SyntheticUnboundedSource{startOffset=5000, endOffset=6000}, 
SyntheticUnboundedSource{startOffset=6000, endOffset=7000}, 
SyntheticUnboundedSource{startOffset=7000, endOffset=8000}, 
SyntheticUnboundedSource{startOffset=8000, endOffset=9000}, 
SyntheticUnboundedSource{startOffset=9000, endOffset=10000}, 
SyntheticUnboundedSource{startOffset=10000, endOffset=11000}, 
SyntheticUnboundedSource{startOffset=11000, endOffset=12000}, 
SyntheticUnboundedSource{startOffset=12000, endOffset=13000}, 
SyntheticUnboundedSource{startOffset=13000, endOffset=14000}, 
SyntheticUnboundedSource{startOffset=14000, endOffset=15000}, 
SyntheticUnboundedSource{startOffset=15000, endOffset=16000}, 
SyntheticUnboundedSource{startOffset=16000, endOffset=17000}, 
SyntheticUnboundedSource{startOffset=17000, endOffset=18000}, 
SyntheticUnboundedSource{startOffset=18000, endOffset=19000}, 
SyntheticUnboundedSource{startOffset=19000, endOffset=20000}]
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input/StripIds as step s2
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect start time metrics as step s3
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Total bytes monitor as step s4
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Window.Into()/Window.Assign as step s5
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Group by key (0) as step s6
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Ungroup and reiterate (0) as step s7
Jan 04, 2023 2:28:57 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect end time metrics (0) as step s8
Jan 04, 2023 2:28:57 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.45.0-SNAPSHOT
Jan 04, 2023 2:28:58 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/2023-01-04_06_28_57-6011848022117644408?project=apache-beam-testing
Jan 04, 2023 2:28:58 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2023-01-04_06_28_57-6011848022117644408
Jan 04, 2023 2:28:58 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 2023-01-04_06_28_57-6011848022117644408
Jan 04, 2023 2:29:05 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2023-01-04T14:29:03.590Z: 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: 
load0tests0java170dataflow0v20streaming0gbk03-jenkins-0104-py1k. 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
Jan 04, 2023 2:29:11 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:11.323Z: Worker configuration: e2-standard-2 in 
us-central1-f.
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.616Z: Expanding SplittableParDo operations into 
optimizable parts.
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.645Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.689Z: Expanding CoGroupByKey operations into 
optimizable parts.
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.759Z: Expanding SplittableProcessKeyed operations 
into optimizable parts.
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.784Z: Expanding GroupByKey operations into streaming 
Read/Write steps
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.839Z: Lifting ValueCombiningMappingFns into 
MergeBucketsMappingFns
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.922Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.958Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:12.996Z: Fusing consumer 
Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.031Z: Fusing consumer 
Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/PairWithRestriction
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.062Z: Fusing consumer Read 
input/ParDo(StripIds)/ParMultiDo(StripIds) into 
Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.097Z: Fusing consumer Collect start time 
metrics/ParMultiDo(TimeMonitor) into Read 
input/ParDo(StripIds)/ParMultiDo(StripIds)
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.123Z: Fusing consumer Total bytes 
monitor/ParMultiDo(ByteMonitor) into Collect start time 
metrics/ParMultiDo(TimeMonitor)
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.152Z: Fusing consumer Window.Into()/Window.Assign 
into Total bytes monitor/ParMultiDo(ByteMonitor)
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.173Z: Fusing consumer Group by key (0)/WriteStream 
into Window.Into()/Window.Assign
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.204Z: Fusing consumer Group by key (0)/MergeBuckets 
into Group by key (0)/ReadStream
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.239Z: Fusing consumer Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate) into Group by key (0)/MergeBuckets
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.272Z: Fusing consumer Collect end time metrics 
(0)/ParMultiDo(TimeMonitor) into Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate)
Jan 04, 2023 2:29:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:13.380Z: Running job using Streaming Engine
Jan 04, 2023 2:29:15 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:14.577Z: Starting 5 ****s in us-central1-f...
Jan 04, 2023 2:29:24 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:21.984Z: 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
Jan 04, 2023 2:29:52 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:51.415Z: Autoscaling: Raised the number of ****s to 1 so 
that the pipeline can catch up with its backlog and keep up with its input rate.
Jan 04, 2023 2:29:52 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:29:51.453Z: Autoscaling: Resized **** pool to 1, though 
goal was 5.  This could be a quota issue.
Jan 04, 2023 2:30:01 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:30:01.144Z: Autoscaling: Raised the number of ****s to 5 so 
that the pipeline can catch up with its backlog and keep up with its input rate.
Jan 04, 2023 2:31:05 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:31:04.078Z: Workers have started successfully.
Jan 04, 2023 2:31:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:31:05.573Z: All ****s have finished the startup processes 
and began to receive work requests.
Jan 04, 2023 2:33:21 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:33:21.550Z: Cleaning up.
Jan 04, 2023 2:33:21 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:33:21.634Z: Stopping **** pool...
Jan 04, 2023 2:33:21 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:33:21.711Z: Stopping **** pool...
Jan 04, 2023 2:35:40 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:35:39.853Z: Autoscaling: Reduced the number of ****s to 0 
based on low average **** CPU utilization, and the pipeline having sufficiently 
low backlog and keeping up with input rate.
Jan 04, 2023 2:35:40 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-01-04T14:35:39.912Z: Worker pool stopped.
Jan 04, 2023 2:35:45 PM org.apache.beam.runners.dataflow.DataflowPipelineJob 
logTerminalState
INFO: Job 2023-01-04_06_28_57-6011848022117644408 finished with status DONE.
Load test results for test (ID): 71a3c79e-f083-4186-b7cc-dc197d1e1338 and 
timestamp: 2023-01-04T14:28:52.975000000Z:
                 Metric:                    Value:
dataflow_v2_java17_runtime_sec                    64.897
dataflow_v2_java17_total_bytes_count                   1.998E9

> Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230104142824
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:7b2f24f25cbeb231431be1ec1864f7524185878de7150594c3fed51d908f3983
WARNING: Successfully resolved tag to sha256, but it is recommended to use 
sha256 directly.
Tag: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230104142824]
- referencing digest: 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:7b2f24f25cbeb231431be1ec1864f7524185878de7150594c3fed51d908f3983]

Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230104142824] 
(referencing 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:7b2f24f25cbeb231431be1ec1864f7524185878de7150594c3fed51d908f3983])].
Removing untagged image 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:cb41c53278b55198a8a187ea97a5e59a43fc4c94377a9c06491481c045aded4f
Digests:
- 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:cb41c53278b55198a8a187ea97a5e59a43fc4c94377a9c06491481c045aded4f
ERROR: (gcloud.container.images.delete) Not found: response: 
{'docker-distribution-api-version': 'registry/2.0', 'content-type': 
'application/json', 'content-encoding': 'gzip', 'date': 'Wed, 04 Jan 2023 
14:35:49 GMT', 'server': 'Docker Registry', 'cache-control': 'private', 
'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'transfer-encoding': 
'chunked', 'status': 404}
Failed to compute blob liveness for manifest: 
'sha256:cb41c53278b55198a8a187ea97a5e59a43fc4c94377a9c06491481c045aded4f': None

> Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 
'<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java17/ws/src/runners/google-cloud-dataflow-java/build.gradle'>
 line: 305

* What went wrong:
Execution failed for task 
':runners:google-cloud-dataflow-java:cleanUpDockerJavaImages'.
> Process 'command './scripts/cleanup_untagged_gcr_images.sh'' 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

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.

See 
https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during 
this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 7m 41s
108 actionable tasks: 9 executed, 99 up-to-date

Publishing build scan...
https://gradle.com/s/e6l65ytqblhok

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