See 
<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Batch_Java11/737/display/redirect>

Changes:


------------------------------------------
[...truncated 57.54 KB...]

#15 [11/16] COPY target/NOTICE /opt/apache/beam/
#15 DONE 0.1s

#16 [12/16] ADD target/third_party_licenses 
/opt/apache/beam/third_party_licenses/
#16 DONE 0.2s

#17 [13/16] COPY target/LICENSE target/options/* /opt/apache/beam/options/
#17 DONE 0.1s

#18 [14/16] COPY target/go-licenses/* 
/opt/apache/beam/third_party_licenses/golang/
#18 DONE 0.1s

#19 [15/16] RUN if [ "true" = "false" ] ; then     rm -rf 
/opt/apache/beam/third_party_licenses ;    fi
#19 DONE 0.3s

#20 [16/16] COPY target/profiler/* /opt/google_cloud_profiler/
#20 DONE 0.1s

#21 exporting to image
#21 exporting layers
#21 exporting layers 0.2s done
#21 writing image 
sha256:2ad7d3963fe8ec2f90073569e5f054a1a3d4417ae2ad87cd41f2ab8cbd5cb695 done
#21 naming to docker.io/apache/beam_java11_sdk:2.49.0.dev done
#21 DONE 0.2s

> 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]
c240e7430289: Preparing
5f70bf18a086: Preparing
2e38b83df1c9: Preparing
367f3ee386df: Preparing
eef73a20ca94: Preparing
20f67a34c4a9: Preparing
d03af0ce93ba: Preparing
e08d8ffdb4a7: Preparing
cfc6ec94af28: Preparing
d3be2c6baf7c: Preparing
1b05cfd033b7: Preparing
2be86372b793: Preparing
223ee2ae49eb: Preparing
d1665b212995: Preparing
7387d08e7db7: Preparing
eeaab7c85b72: Preparing
ddcd187dc7b8: Preparing
8d8fafa18e50: Preparing
cdd7c7392317: Preparing
e08d8ffdb4a7: Waiting
cfc6ec94af28: Waiting
1b05cfd033b7: Waiting
20f67a34c4a9: Waiting
d03af0ce93ba: Waiting
2be86372b793: Waiting
d3be2c6baf7c: Waiting
eeaab7c85b72: Waiting
8d8fafa18e50: Waiting
223ee2ae49eb: Waiting
ddcd187dc7b8: Waiting
5f70bf18a086: Layer already exists
20f67a34c4a9: Pushed
367f3ee386df: Pushed
2e38b83df1c9: Pushed
c240e7430289: Pushed
eef73a20ca94: Pushed
d03af0ce93ba: Pushed
cfc6ec94af28: Pushed
d3be2c6baf7c: Pushed
1b05cfd033b7: Pushed
e08d8ffdb4a7: Pushed
eeaab7c85b72: Layer already exists
ddcd187dc7b8: Layer already exists
8d8fafa18e50: Layer already exists
cdd7c7392317: Layer already exists
2be86372b793: Pushed
223ee2ae49eb: Pushed
7387d08e7db7: Pushed
d1665b212995: Pushed
20230628080241: digest: 
sha256:63250e3921a7d8fc68e64766ce1613501285ff5b9948ab48931f4d9d76f545c2 size: 
4297

> Task :sdks:java:testing:load-tests:run
Jun 28, 2023 8:03:27 AM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Jun 28, 2023 8:03:28 AM 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.
Jun 28, 2023 8:03:28 AM 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.
Jun 28, 2023 8:03:31 AM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 232 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Jun 28, 2023 8:03:32 AM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 232 files cached, 0 files newly uploaded in 0 
seconds
Jun 28, 2023 8:03:32 AM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Jun 28, 2023 8:03:32 AM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <98540 bytes, hash 
045a7976821227cfec7cfc0add91238ba5bf4a4ce918a0bdb079fc9c471a24f8> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-BFp5doISJ8_sfPwK3ZEji6W_SkzpGKC9sHn8nEcaJPg.pb
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect start time metrics as step s2
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Total bytes monitor as step s3
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Window.Into()/Window.Assign as step s4
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Group by key (0) as step s5
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Ungroup and reiterate (0) as step s6
Jun 28, 2023 8:03:34 AM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Collect end time metrics (0) as step s7
Jun 28, 2023 8:03:34 AM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.49.0-SNAPSHOT
Jun 28, 2023 8:03:34 AM 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-06-28_01_03_34-11679934504847734970?project=apache-beam-testing
Jun 28, 2023 8:03:34 AM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2023-06-28_01_03_34-11679934504847734970
Jun 28, 2023 8:03:34 AM 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-06-28_01_03_34-11679934504847734970
Jun 28, 2023 8:03:37 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2023-06-28T08:03:36.745Z: 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: 
load0tests0java110dataflow0v20batch0gbk01-jenkins-06280803-xy0v. 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
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:43.056Z: Worker configuration: e2-standard-2 in 
us-central1-a.
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.287Z: Expanding SplittableParDo operations into 
optimizable parts.
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.318Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.395Z: Expanding CoGroupByKey operations into 
optimizable parts.
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.463Z: Expanding GroupByKey operations into 
optimizable parts.
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.527Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.555Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.587Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.619Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.651Z: Fusing consumer Collect start time 
metrics/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.683Z: Fusing consumer Total bytes 
monitor/ParMultiDo(ByteMonitor) into Collect start time 
metrics/ParMultiDo(TimeMonitor)
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.714Z: Fusing consumer Window.Into()/Window.Assign 
into Total bytes monitor/ParMultiDo(ByteMonitor)
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.737Z: Fusing consumer Group by key (0)/Write into 
Window.Into()/Window.Assign
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.768Z: Fusing consumer Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate) into Group by key (0)/Read
Jun 28, 2023 8:03:44 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:44.804Z: Fusing consumer Collect end time metrics 
(0)/ParMultiDo(TimeMonitor) into Ungroup and reiterate 
(0)/ParMultiDo(UngroupAndReiterate)
Jun 28, 2023 8:03:46 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:45.127Z: 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
Jun 28, 2023 8:03:46 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:03:45.203Z: Starting 5 ****s in us-central1-a...
Jun 28, 2023 8:04:07 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:04:07.393Z: 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
Jun 28, 2023 8:04:32 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:04:32.746Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Jun 28, 2023 8:05:21 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:20.967Z: Workers have started successfully.
Jun 28, 2023 8:05:31 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:30.310Z: All ****s have finished the startup processes 
and began to receive work requests.
Jun 28, 2023 8:05:34 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:33.620Z: 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
Jun 28, 2023 8:05:34 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:33.735Z: Executing operation Group by key (0)/Create
Jun 28, 2023 8:05:36 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:34.188Z: Finished operation Group by key (0)/Create
Jun 28, 2023 8:05:36 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:05:34.317Z: 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
Jun 28, 2023 8:06:15 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:15.032Z: 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
Jun 28, 2023 8:06:15 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:15.092Z: Executing operation Group by key (0)/Close
Jun 28, 2023 8:06:31 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:29.409Z: Finished operation Group by key (0)/Close
Jun 28, 2023 8:06:31 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:29.467Z: Executing operation Group by key 
(0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end 
time metrics (0)/ParMultiDo(TimeMonitor)
Jun 28, 2023 8:06:54 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:54.398Z: Finished operation Group by key 
(0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end 
time metrics (0)/ParMultiDo(TimeMonitor)
Jun 28, 2023 8:06:55 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:54.525Z: Cleaning up.
Jun 28, 2023 8:06:55 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:06:54.591Z: Stopping **** pool...
Jun 28, 2023 8:09:27 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:09:27.300Z: Autoscaling: Resized **** pool from 5 to 0.
Jun 28, 2023 8:09:29 AM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2023-06-28T08:09:27.336Z: Worker pool stopped.
Jun 28, 2023 8:09:33 AM org.apache.beam.runners.dataflow.DataflowPipelineJob 
logTerminalState
INFO: Job 2023-06-28_01_03_34-11679934504847734970 finished with status DONE.
Load test results for test (ID): 5b2c06a1-1f30-45ea-8b04-9c4a2f59bf88 and 
timestamp: 2023-06-28T08:03:28.531000000Z:
                 Metric:                    Value:
dataflow_v2_java11_runtime_sec                    78.921
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:20230628080241
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:63250e3921a7d8fc68e64766ce1613501285ff5b9948ab48931f4d9d76f545c2
ERROR: gcloud crashed (ConnectionError): HTTPSConnectionPool(host='us.gcr.io', 
port=443): Max retries exceeded with url: /v2/ (Caused by 
NewConnectionError('<urllib3.connection.HTTPSConnection object at 
0x7f4000e81340>: Failed to establish a new connection: [Errno 101] Network is 
unreachable'))

If you would like to report this issue, please run the following command:
  gcloud feedback

To check gcloud for common problems, please run the following command:
  gcloud info --run-diagnostics

> 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: 302

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

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 9m 19s
117 actionable tasks: 78 executed, 35 from cache, 4 up-to-date

Publishing build scan...
https://ge.apache.org/s/4ffvdnqoov4qk

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