You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@beam.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2022/07/11 12:45:03 UTC
Build failed in Jenkins: beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11 #386
See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/386/display/redirect?page=changes>
Changes:
[noreply] Parallelizable DataFrame/Series mean (#22174)
------------------------------------------
[...truncated 47.42 KB...]
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 :release:go-licenses:java:createLicenses
> Task :sdks:java:container:java11:copyGolangLicenses
> 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]
29df080a2e12: Preparing
0932f112c8c3: Preparing
55f6806cd6f7: Preparing
6e847dc25e37: Preparing
910bc7f562f7: Preparing
d5e5a3f22df8: Preparing
e544f567633c: Preparing
36762f20564e: Preparing
8115fcb764e4: Preparing
e857b0faa926: Preparing
c6abaa266fab: Preparing
00e843599a5c: Preparing
32d73425612d: Preparing
158cd0b95a67: Preparing
38bdad2c800c: Preparing
7e145627a1fb: Preparing
6812ae0d9f23: Preparing
369123a7ed65: Preparing
5afd661c6106: Preparing
66183893ba24: Preparing
6840c8ff46bd: Preparing
e544f567633c: Waiting
97d5fec864d8: Preparing
36762f20564e: Waiting
c6abaa266fab: Waiting
d5e5a3f22df8: Waiting
369123a7ed65: Waiting
8115fcb764e4: Waiting
00e843599a5c: Waiting
e857b0faa926: Waiting
158cd0b95a67: Waiting
5afd661c6106: Waiting
7e145627a1fb: Waiting
32d73425612d: Waiting
66183893ba24: Waiting
38bdad2c800c: Waiting
6840c8ff46bd: Waiting
97d5fec864d8: Waiting
910bc7f562f7: Pushed
6e847dc25e37: Pushed
0932f112c8c3: Pushed
55f6806cd6f7: Pushed
29df080a2e12: Pushed
e544f567633c: Pushed
36762f20564e: Pushed
e857b0faa926: Pushed
d5e5a3f22df8: Pushed
00e843599a5c: Pushed
8115fcb764e4: Pushed
7e145627a1fb: Layer already exists
c6abaa266fab: Pushed
6812ae0d9f23: Layer already exists
369123a7ed65: Layer already exists
5afd661c6106: Layer already exists
66183893ba24: Layer already exists
6840c8ff46bd: Layer already exists
97d5fec864d8: Layer already exists
158cd0b95a67: Pushed
38bdad2c800c: Pushed
32d73425612d: Pushed
20220711124133: digest: sha256:e74d2e2b2b31c4f1b2598dbaf33268c9181c7ee6dcaa9b53a6f5e0171a2b7876 size: 4935
> Task :sdks:java:testing:load-tests:run
Jul 11, 2022 12:42:43 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Jul 11, 2022 12:42:44 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.
Jul 11, 2022 12:42:45 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: ParDo(TimeMonitor)
Jul 11, 2022 12:42:45 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.
Jul 11, 2022 12:42:47 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements
INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location to prepare for execution.
Jul 11, 2022 12:42:48 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements
INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 0 seconds
Jul 11, 2022 12:42:48 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/
Jul 11, 2022 12:42:48 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage
INFO: Uploading <112554 bytes, hash 83213c14d58fc97c14aedc36ac6ee02bb36537f2a9877ab251f51a37a4a19618> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-gyE8FNWPyXwUrtw2rG7gK7NlN_Kph3qyUfUaN6Shlhg.pb
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 1 as step s5
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 2 as step s6
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 3 as step s7
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 4 as step s8
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 5 as step s9
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 6 as step s10
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 7 as step s11
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 8 as step s12
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 9 as step s13
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s14
Jul 11, 2022 12:42:50 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.41.0-SNAPSHOT
Jul 11, 2022 12:42: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/2022-07-11_05_42_50-3682351663314168175?project=apache-beam-testing
Jul 11, 2022 12:42:52 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-07-11_05_42_50-3682351663314168175
Jul 11, 2022 12:42: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 2022-07-11_05_42_50-3682351663314168175
Jul 11, 2022 12:42:55 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-07-11T12:42:54.805Z: 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-071112-t6ax. 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
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:42:59.334Z: Worker configuration: e2-standard-2 in us-central1-b.
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:42:59.937Z: Expanding SplittableParDo operations into optimizable parts.
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:42:59.966Z: Expanding CollectionToSingleton operations into optimizable parts.
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.032Z: Expanding CoGroupByKey operations into optimizable parts.
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.072Z: Expanding GroupByKey operations into optimizable parts.
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.148Z: Fusing adjacent ParDo, Read, Write, and Flatten operations
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.177Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.208Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.244Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.269Z: Fusing consumer ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.306Z: Fusing consumer ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.362Z: Fusing consumer Step: 0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.397Z: Fusing consumer Step: 1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.454Z: Fusing consumer Step: 2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.487Z: Fusing consumer Step: 3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.520Z: Fusing consumer Step: 4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.601Z: Fusing consumer Step: 5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.634Z: Fusing consumer Step: 6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.669Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.702Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.736Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.760Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:01.114Z: 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
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:01.192Z: Starting 5 ****s in us-central1-b...
Jul 11, 2022 12:43:33 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:32.732Z: 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
Jul 11, 2022 12:43:36 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:35.178Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s).
Jul 11, 2022 12:44:39 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:39.378Z: Workers have started successfully.
Jul 11, 2022 12:44:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:58.731Z: 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
Jul 11, 2022 12:44:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:58.855Z: Executing operation Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step: 0/ParMultiDo(CounterOperation)+Step: 1/ParMultiDo(CounterOperation)+Step: 2/ParMultiDo(CounterOperation)+Step: 3/ParMultiDo(CounterOperation)+Step: 4/ParMultiDo(CounterOperation)+Step: 5/ParMultiDo(CounterOperation)+Step: 6/ParMultiDo(CounterOperation)+Step: 7/ParMultiDo(CounterOperation)+Step: 8/ParMultiDo(CounterOperation)+Step: 9/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor)
The message received from the daemon indicates that the daemon has disappeared.
Build request sent: Build{id=13660534-573f-4929-9867-a83fda6b9ba7, 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: 647387
log file: /home/jenkins/.gradle/daemon/7.4/daemon-647387.out.log
----- Last 20 lines from daemon log file - daemon-647387.out.log -----
INFO: 2022-07-11T12:43:00.702Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.736Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:00.760Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation)
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:01.114Z: 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
Jul 11, 2022 12:43:02 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:01.192Z: Starting 5 ****s in us-central1-b...
Jul 11, 2022 12:43:33 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:32.732Z: 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
Jul 11, 2022 12:43:36 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:43:35.178Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s).
Jul 11, 2022 12:44:39 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:39.378Z: Workers have started successfully.
Jul 11, 2022 12:44:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:58.731Z: 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
Jul 11, 2022 12:44:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-07-11T12:44:58.855Z: Executing operation Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step: 0/ParMultiDo(CounterOperation)+Step: 1/ParMultiDo(CounterOperation)+Step: 2/ParMultiDo(CounterOperation)+Step: 3/ParMultiDo(CounterOperation)+Step: 4/ParMultiDo(CounterOperation)+Step: 5/ParMultiDo(CounterOperation)+Step: 6/ParMultiDo(CounterOperation)+Step: 7/ParMultiDo(CounterOperation)+Step: 8/ParMultiDo(CounterOperation)+Step: 9/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor)
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
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Jenkins build is back to normal : beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11 #387
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/387/display/redirect?page=changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org