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

Changes:

[noreply] Merge pull request #26006: Google Cloud libraries BOM 26.11.0


------------------------------------------
[...truncated 461.04 KB...]
#20 DONE 0.4s

#21 [17/18] RUN if [ "true" = "false" ] ; then     rm -rf 
/opt/apache/beam/third_party_licenses ;    fi
#21 DONE 0.4s

#22 [18/18] COPY target/profiler/* /opt/google_cloud_profiler/
#22 DONE 0.1s

#23 exporting to image
#23 exporting layers
#23 exporting layers 0.3s done
#23 writing image 
sha256:c1415fee0e74122fd5437b008e73239b76b6449bebc4dba99eea3ceae975bce9 done
#23 naming to docker.io/apache/beam_java11_sdk:2.47.0.dev done
#23 DONE 0.3s

> 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]
cd691783a0d2: Preparing
5f70bf18a086: Preparing
63150e696274: Preparing
fbbc62120111: Preparing
0c7b54e81aa4: Preparing
14422dc4e650: Preparing
60e66a8a1c3c: Preparing
54bf5c01b540: Preparing
bc24ff100368: Preparing
981ccd66ffe5: Preparing
ed62ba53405d: Preparing
a830e48ab971: Preparing
3eb4b8a2250c: Preparing
7780705bef16: Preparing
3ae9fea8e5be: Preparing
a2b822e0abfb: Preparing
6418513c2a68: Preparing
749d6cfaa5eb: Preparing
8ac55e7a3c46: Preparing
04d1dcab20cb: Preparing
b93c1bd012ab: Preparing
54bf5c01b540: Waiting
bc24ff100368: Waiting
981ccd66ffe5: Waiting
ed62ba53405d: Waiting
a830e48ab971: Waiting
14422dc4e650: Waiting
3eb4b8a2250c: Waiting
7780705bef16: Waiting
a2b822e0abfb: Waiting
60e66a8a1c3c: Waiting
3ae9fea8e5be: Waiting
b93c1bd012ab: Waiting
749d6cfaa5eb: Waiting
8ac55e7a3c46: Waiting
04d1dcab20cb: Waiting
5f70bf18a086: Layer already exists
0c7b54e81aa4: Pushed
14422dc4e650: Pushed
fbbc62120111: Pushed
cd691783a0d2: Pushed
bc24ff100368: Pushed
54bf5c01b540: Pushed
63150e696274: Pushed
60e66a8a1c3c: Pushed
ed62ba53405d: Pushed
3eb4b8a2250c: Pushed
a830e48ab971: Pushed
981ccd66ffe5: Pushed
749d6cfaa5eb: Layer already exists
8ac55e7a3c46: Layer already exists
7780705bef16: Pushed
04d1dcab20cb: Layer already exists
b93c1bd012ab: Layer already exists
3ae9fea8e5be: Pushed
a2b822e0abfb: Pushed
6418513c2a68: Pushed
20230402143924: digest: 
sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50 size: 
4712

> Task :sdks:java:testing:load-tests:run
Apr 02, 2023 2:39:45 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Apr 02, 2023 2:39:45 PM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from 
the classpath: will stage 230 files. Enable logging at DEBUG level to see which 
files will be staged.
Apr 02, 2023 2:39:46 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.
Apr 02, 2023 2:39:48 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 230 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Apr 02, 2023 2:39:49 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 230 files cached, 0 files newly uploaded in 0 
seconds
Apr 02, 2023 2:39:49 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Apr 02, 2023 2:39:49 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <97872 bytes, hash 
d5c653995a3634948dd11cccdbfdbcaeab053b0ba7f3eb1d5459a247f6824ed3> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-1cZTmVo2NJSN0RzM2_28rqsFOwun8-sdVFmiR_aCTtM.pb
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect start time metrics as step s2
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Total bytes monitor as step s3
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Window.Into()/Window.Assign as step s4
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Group by key (0) as step s5
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Ungroup and reiterate (0) as step s6
Apr 02, 2023 2:39:51 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect end time metrics (0) as step s7
Apr 02, 2023 2:39:51 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.47.0-SNAPSHOT
Apr 02, 2023 2:39:52 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-04-02_07_39_51-10848680134568275534?project=apache-beam-testing
Apr 02, 2023 2:39:52 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2023-04-02_07_39_51-10848680134568275534
Apr 02, 2023 2:39:52 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-04-02_07_39_51-10848680134568275534
Apr 02, 2023 2:39:55 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2023-04-02T14:39:54.602Z: 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: 
load0tests0java110dataflow0v20batch0gbk07-jenkins-04021439-zhf5. 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
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:39:59.794Z: Worker configuration: e2-standard-2 in 
us-central1-b.
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:00.944Z: Expanding SplittableParDo operations into 
optimizable parts.
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:00.970Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.047Z: Expanding CoGroupByKey operations into 
optimizable parts.
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.097Z: Expanding GroupByKey operations into 
optimizable parts.
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.143Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.162Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.183Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.205Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.227Z: Fusing consumer Collect start time 
metrics/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.241Z: Fusing consumer Total bytes 
monitor/ParMultiDo(ByteMonitor) into Collect start time 
metrics/ParMultiDo(TimeMonitor)
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.264Z: Fusing consumer Window.Into()/Window.Assign 
into Total bytes monitor/ParMultiDo(ByteMonitor)
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.286Z: Fusing consumer Group by key (0)/Write into 
Window.Into()/Window.Assign
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.301Z: Fusing consumer Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate) into Group by key (0)/Read
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.326Z: Fusing consumer Collect end time metrics 
(0)/ParMultiDo(TimeMonitor) into Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate)
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.561Z: 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
Apr 02, 2023 2:40:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:01.613Z: Starting 5 ****s in us-central1-b...
Apr 02, 2023 2:40:29 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:29.580Z: 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
Apr 02, 2023 2:40:41 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:40:39.424Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Apr 02, 2023 2:41:32 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:30.354Z: Workers have started successfully.
Apr 02, 2023 2:41:41 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:39.537Z: All ****s have finished the startup processes 
and began to receive work requests.
Apr 02, 2023 2:41:47 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:44.406Z: 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
Apr 02, 2023 2:41:47 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:44.485Z: Executing operation Group by key (0)/Create
Apr 02, 2023 2:41:47 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:45.815Z: Finished operation Group by key (0)/Create
Apr 02, 2023 2:41:47 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:41:45.901Z: Executing operation 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+Collect
 start time metrics/ParMultiDo(TimeMonitor)+Total bytes 
monitor/ParMultiDo(ByteMonitor)+Window.Into()/Window.Assign+Group by key 
(0)/Write
Apr 02, 2023 2:42:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:12.674Z: Finished operation 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+Collect
 start time metrics/ParMultiDo(TimeMonitor)+Total bytes 
monitor/ParMultiDo(ByteMonitor)+Window.Into()/Window.Assign+Group by key 
(0)/Write
Apr 02, 2023 2:42:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:12.728Z: Executing operation Group by key (0)/Close
Apr 02, 2023 2:42:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:12.773Z: Finished operation Group by key (0)/Close
Apr 02, 2023 2:42:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:12.810Z: Executing operation Group by key 
(0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end 
time metrics (0)/ParMultiDo(TimeMonitor)
Apr 02, 2023 2:42:30 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:28.681Z: Finished operation Group by key 
(0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end 
time metrics (0)/ParMultiDo(TimeMonitor)
Apr 02, 2023 2:42:30 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:28.773Z: Cleaning up.
Apr 02, 2023 2:42:30 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:42:28.831Z: Stopping **** pool...
Apr 02, 2023 2:44:39 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:44:38.130Z: Autoscaling: Resized **** pool from 5 to 0.
Apr 02, 2023 2:44:39 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-04-02T14:44:38.161Z: Worker pool stopped.
Apr 02, 2023 2:44:43 PM org.apache.beam.runners.dataflow.DataflowPipelineJob 
logTerminalState
INFO: Job 2023-04-02_07_39_51-10848680134568275534 finished with status DONE.
Load test results for test (ID): 4e101a6e-1ed3-4e99-9a09-e2e5aba88d60 and 
timestamp: 2023-04-02T14:39:46.275000000Z:
                 Metric:                    Value:
dataflow_v2_java11_runtime_sec                    39.251
dataflow_v2_java11_total_bytes_count                     2.0E9

> Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230402143924
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50
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:20230402143924]
- referencing digest: 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50]

Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230402143924] 
(referencing 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50])].
Removing untagged image 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50
Digests:
- 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50
ERROR: (gcloud.container.images.delete) Not found: response: 
{'docker-distribution-api-version': 'registry/2.0', 'content-type': 
'application/json', 'content-encoding': 'gzip', 'date': 'Sun, 02 Apr 2023 
14:44:48 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:17cf12256095121eab370569ae796d4765362067b34a401ccee42650b52a4b50': 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_Batch_Java11/ws/src/runners/google-cloud-dataflow-java/build.gradle'>
 line: 306

* 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 5m 41s
112 actionable tasks: 9 executed, 103 up-to-date

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

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