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

Changes:

[alexey.inkin] Add an abstract layer for analytics, fix logging change of 
snippet, fix

[damondouglas] Implement PubsubSchemaTransformMessageToFactory

[bulat.safiullin] [Website] add scroll-spy to body in case-studies/baseof.html

[noreply] Update issue bot to javascript and add label management (#22067)

[noreply] Clean up issue management doc page

[noreply] [BEAM-13015, #21250, fixes #22053] Improve PCollectionConsumerRegistry

[noreply] sharding GCP IO tests from the javaPostCommit task (#21800)

[noreply] Bump cloud.google.com/go/storage from 1.22.1 to 1.23.0 in /sdks 
(#22038)

[noreply] Followup sharding javaPostCommit (#22081)

[noreply] remove mention of dill in release notes as it's not relevant. (#22087)

[noreply] [#21634] Add comments on FieldValueGetter. (#21982)

[noreply] Bump google.golang.org/api from 0.85.0 to 0.86.0 in /sdks (#22092)

[noreply] [BEAM-6597] Replace ProgressRequestCallback with 
BundleProgressReporter

[noreply] [Go SDK] Go Lint fixes  (#21967)

[noreply] Fix #21869: Close GRPC connections on cancel (#21874)

[noreply] Add FlatMap(<builtin>) known issue to 2.40.0 blog (#22101)

[noreply] [BEAM-14347] Update docs to prefer generic registration functions

[Andrew Pilloud] Projection Pushdown optimizer on by default

[noreply] Merge pull request #21752 from Feature/beam 13852 reimplement with

[noreply] Change wording of Pytorch LM example (#22099)

[noreply] Fix missing model_params in Pytorch docstring  (#22100)

[noreply] Test and fix FlatMap(<builtin>) issue (#22104)

[noreply] Fix InputStream on platform with 4 bytie long (#22107)


------------------------------------------
[...truncated 47.04 KB...]
INFO:root:pull_licenses_java.py succeed. It took 11.817739 seconds with 16 
threads.
Copying licenses from 
<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src/sdks/java/container/build/target/java_third_party_licenses>
 to 
<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src/sdks/java/container/build/target/third_party_licenses.>
Finished license_scripts.sh

> Task :sdks:java:container:goPrepare UP-TO-DATE
> 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 :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]
1a0a45f25367: Preparing
ce0fa83fd181: Preparing
863c7390fcb6: Preparing
3e475567d4f1: Preparing
ee7367e97474: Preparing
3e23d1f83177: Preparing
538ebfa9ca5c: Preparing
3ce27f677cf1: Preparing
5afef5b687f1: Preparing
e33c253a2409: Preparing
c4f92754f0ab: Preparing
98642165bfec: Preparing
e9055101af0e: Preparing
bdd2f8f35d2d: Preparing
efdf14b3c7cc: Preparing
7e145627a1fb: Preparing
6812ae0d9f23: Preparing
369123a7ed65: Preparing
5afd661c6106: Preparing
c4f92754f0ab: Waiting
66183893ba24: Preparing
538ebfa9ca5c: Waiting
6840c8ff46bd: Preparing
98642165bfec: Waiting
97d5fec864d8: Preparing
3e23d1f83177: Waiting
3ce27f677cf1: Waiting
e33c253a2409: Waiting
5afef5b687f1: Waiting
5afd661c6106: Waiting
6840c8ff46bd: Waiting
369123a7ed65: Waiting
e9055101af0e: Waiting
66183893ba24: Waiting
7e145627a1fb: Waiting
6812ae0d9f23: Waiting
efdf14b3c7cc: Waiting
3e475567d4f1: Pushed
ee7367e97474: Pushed
ce0fa83fd181: Pushed
863c7390fcb6: Pushed
1a0a45f25367: Pushed
538ebfa9ca5c: Pushed
3ce27f677cf1: Pushed
e33c253a2409: Pushed
5afef5b687f1: Pushed
3e23d1f83177: Pushed
c4f92754f0ab: Pushed
98642165bfec: Pushed
7e145627a1fb: Layer already exists
6812ae0d9f23: Layer already exists
369123a7ed65: Layer already exists
5afd661c6106: Layer already exists
66183893ba24: Layer already exists
6840c8ff46bd: Layer already exists
97d5fec864d8: Layer already exists
bdd2f8f35d2d: Pushed
efdf14b3c7cc: Pushed
e9055101af0e: Pushed
20220630124131: digest: 
sha256:1b41a12ab1cdae2e0639ab520032bb4d07c4276a2c8fb7976735b4d4ece9860c size: 
4935

> Task :sdks:java:testing:load-tests:run
Jun 30, 2022 12:42:55 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Jun 30, 2022 12:42:56 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.
Jun 30, 2022 12:42:57 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: 
ParDo(TimeMonitor)
Jun 30, 2022 12:42:57 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.
Jun 30, 2022 12:43:01 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Jun 30, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 1 
seconds
Jun 30, 2022 12:43:02 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Jun 30, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <112554 bytes, hash 
45783663bbe4ba267acb5c7253824130a7402cd4ac4703e27529882f81c95109> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-RXg2Y7vkuiZ6y1xyU4JBMKdALNSsRwPidSmIL4HJUQk.pb
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 1 as step s5
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 2 as step s6
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 3 as step s7
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 4 as step s8
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 5 as step s9
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 6 as step s10
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 7 as step s11
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 8 as step s12
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 9 as step s13
Jun 30, 2022 12:43:04 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s14
Jun 30, 2022 12:43:04 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.41.0-SNAPSHOT
Jun 30, 2022 12:43:04 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-06-30_05_43_04-9027702101084426097?project=apache-beam-testing
Jun 30, 2022 12:43:04 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-06-30_05_43_04-9027702101084426097
Jun 30, 2022 12:43:04 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-06-30_05_43_04-9027702101084426097
Jun 30, 2022 12:43:16 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-06-30T12:43:14.884Z: 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-063012-fidd. 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 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:19.562Z: Worker configuration: e2-standard-2 in 
us-central1-f.
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.303Z: Expanding SplittableParDo operations into 
optimizable parts.
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.343Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.408Z: Expanding CoGroupByKey operations into 
optimizable parts.
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.440Z: Expanding GroupByKey operations into 
optimizable parts.
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.514Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.552Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.586Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.639Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.674Z: Fusing consumer 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.709Z: Fusing consumer 
ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.730Z: Fusing consumer Step: 
0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.761Z: Fusing consumer Step: 
1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.796Z: Fusing consumer Step: 
2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.853Z: Fusing consumer Step: 
3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.882Z: Fusing consumer Step: 
4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.908Z: Fusing consumer Step: 
5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.960Z: Fusing consumer Step: 
6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:20.985Z: Fusing consumer Step: 
7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.022Z: Fusing consumer Step: 
8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.057Z: Fusing consumer Step: 
9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.081Z: Fusing consumer 
ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 
9/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.426Z: 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 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.499Z: Starting 5 ****s in us-central1-f...
Jun 30, 2022 12:43:40 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:39.688Z: 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 30, 2022 12:43:58 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:56.004Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Jun 30, 2022 12:44:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:44:58.824Z: Workers have started successfully.

> 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=502f50d7-44af-42e9-80cd-62a1dc446a92, 
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: 2378953
  log file: /home/jenkins/.gradle/daemon/7.4/daemon-2378953.out.log
----- Last  20 lines from daemon log file - daemon-2378953.out.log -----
INFO: 2022-06-30T12:43:20.985Z: Fusing consumer Step: 
7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.022Z: Fusing consumer Step: 
8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.057Z: Fusing consumer Step: 
9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.081Z: Fusing consumer 
ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 
9/ParMultiDo(CounterOperation)
Jun 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.426Z: 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 30, 2022 12:43:22 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:21.499Z: Starting 5 ****s in us-central1-f...
Jun 30, 2022 12:43:40 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:39.688Z: 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 30, 2022 12:43:58 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:43:56.004Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Jun 30, 2022 12:44:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-06-30T12:44:58.824Z: Workers have started successfully.
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220630124131
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:1b41a12ab1cdae2e0639ab520032bb4d07c4276a2c8fb7976735b4d4ece9860c
Daemon vm is shutting down... The daemon has exited normally or was terminated 
in response to a user interrupt.
----- 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:20220630124131
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:1b41a12ab1cdae2e0639ab520032bb4d07c4276a2c8fb7976735b4d4ece9860c
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