See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java17/121/display/redirect?page=changes>
Changes: [andyye333] Change func to PTransform [noreply] Populate actual dataflow job id to bigquery write trace id (#17130) [relax] mark static thread as a daemon thread [noreply] [BEAM-13866] Add miscellaneous exec unit tests (#17363) ------------------------------------------ [...truncated 45.40 KB...] - Gradle detected a problem with the following location: '<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_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.4/userguide/validation_problems.html#implicit_dependency for more details about this problem. > Task :release:go-licenses:java:dockerRun + go-licenses save github.com/apache/beam/sdks/java/container --save_path=/output/licenses + go-licenses csv github.com/apache/beam/sdks/java/container + tee /output/licenses/list.csv google.golang.org/protobuf,https://go.googlesource.com/protobuf/+/refs/heads/master/LICENSE,BSD-3-Clause google.golang.org/genproto/googleapis/rpc/status,https://github.com/googleapis/go-genproto/blob/master/LICENSE,Apache-2.0 golang.org/x/text,https://go.googlesource.com/text/+/refs/heads/master/LICENSE,BSD-3-Clause github.com/apache/beam/sdks/java/container,https://github.com/apache/beam/blob/master/LICENSE,Apache-2.0 github.com/apache/beam/sdks/go/pkg/beam,https://github.com/apache/beam/blob/master/sdks/go/README.md,Apache-2.0 golang.org/x/net,https://go.googlesource.com/net/+/refs/heads/master/LICENSE,BSD-3-Clause github.com/golang/protobuf,https://github.com/golang/protobuf/blob/master/LICENSE,BSD-3-Clause google.golang.org/grpc,https://github.com/grpc/grpc-go/blob/master/LICENSE,Apache-2.0 golang.org/x/sys,https://go.googlesource.com/sys/+/refs/heads/master/LICENSE,BSD-3-Clause + chmod -R a+w /output/licenses > Task :release:go-licenses:java:createLicenses > Task :sdks:java:container:java17:copyGolangLicenses > 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] 0dbb4606f08f: Preparing 14f6f0081e66: Preparing b0b22228f7c7: Preparing 152d7ecaa345: Preparing 4cd320c6487e: Preparing befccf1aa624: Preparing 3bd3ac1b7ea8: Preparing 3be864074479: Preparing b4a97ad2a240: Preparing 2ece79d4ead7: Preparing b84893f6ec84: Preparing c6e91511a401: Preparing f6c887c70d0b: Preparing c629906cb674: Preparing 459e157a5baa: Preparing 3bc383470c05: Preparing e93827457889: Preparing 08fa02ce37eb: Preparing a037458de4e0: Preparing bafdbe68e4ae: Preparing a13c519c6361: Preparing c629906cb674: Waiting f6c887c70d0b: Waiting a037458de4e0: Waiting bafdbe68e4ae: Waiting 459e157a5baa: Waiting 3bc383470c05: Waiting e93827457889: Waiting 08fa02ce37eb: Waiting a13c519c6361: Waiting b4a97ad2a240: Waiting 3bd3ac1b7ea8: Waiting 2ece79d4ead7: Waiting befccf1aa624: Waiting 3be864074479: Waiting 14f6f0081e66: Pushed b0b22228f7c7: Pushed 152d7ecaa345: Pushed 4cd320c6487e: Pushed 0dbb4606f08f: Pushed 3be864074479: Pushed 3bd3ac1b7ea8: Pushed 2ece79d4ead7: Pushed c6e91511a401: Pushed b4a97ad2a240: Pushed b84893f6ec84: Pushed befccf1aa624: 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 c629906cb674: Pushed 459e157a5baa: Pushed f6c887c70d0b: Pushed 20220420125829: digest: sha256:43299c4ce403370094182fbb338e2daba0985e538a5d84f02e563e96a38a23a9 size: 4729 > Task :sdks:java:testing:load-tests:run Apr 20, 2022 1:00:41 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create INFO: No stagingLocation provided, falling back to gcpTempLocation Apr 20, 2022 1:00:42 PM org.apache.beam.runners.dataflow.DataflowRunner fromOptions INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from the classpath: will stage 208 files. Enable logging at DEBUG level to see which files will be staged. Apr 20, 2022 1:00:43 PM org.apache.beam.sdk.Pipeline validate WARNING: The following transforms do not have stable unique names: ParDo(TimeMonitor) Apr 20, 2022 1:00:43 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 20, 2022 1:00:45 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Uploading 208 files from PipelineOptions.filesToStage to staging location to prepare for execution. Apr 20, 2022 1:00:45 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Staging files complete: 208 files cached, 0 files newly uploaded in 0 seconds Apr 20, 2022 1:00:45 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/ Apr 20, 2022 1:00:45 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage INFO: Uploading <107601 bytes, hash 21f729094bf255ec28d95ae3659fd0161688a4bc4a7fdc3d7a8df368ff2e4fc4> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-IfcpCUvyVewo2VrjZZ_QFhaIpLxKf9w9eo3zaP8uT8Q.pb Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input as step s1 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor) as step s2 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(ByteMonitor) as step s3 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 0 as step s4 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 1 as step s5 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 2 as step s6 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 3 as step s7 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 4 as step s8 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 5 as step s9 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 6 as step s10 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 7 as step s11 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 8 as step s12 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 9 as step s13 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor)2 as step s14 Apr 20, 2022 1:00:47 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Dataflow SDK version: 2.39.0-SNAPSHOT Apr 20, 2022 1:00:48 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-04-20_06_00_47-9508044923897138893?project=apache-beam-testing Apr 20, 2022 1:00:48 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Submitted job: 2022-04-20_06_00_47-9508044923897138893 Apr 20, 2022 1:00:48 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-04-20_06_00_47-9508044923897138893 Apr 20, 2022 1:00:51 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2022-04-20T13:00:49.921Z: 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: load0tests0java170dataflow0v20batch0pardo01-jenkins-042013-cpz6. 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 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:54.608Z: Worker configuration: e2-standard-2 in us-central1-b. Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.433Z: Expanding SplittableParDo operations into optimizable parts. Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.466Z: Expanding CollectionToSingleton operations into optimizable parts. Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.528Z: Expanding CoGroupByKey operations into optimizable parts. Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.566Z: Expanding GroupByKey operations into optimizable parts. Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.633Z: Fusing adjacent ParDo, Read, Write, and Flatten operations Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.658Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.689Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.721Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.753Z: Fusing consumer ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.785Z: Fusing consumer ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.851Z: Fusing consumer Step: 0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.889Z: Fusing consumer Step: 1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.923Z: Fusing consumer Step: 2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.954Z: Fusing consumer Step: 3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:55.986Z: Fusing consumer Step: 4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.019Z: Fusing consumer Step: 5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.040Z: Fusing consumer Step: 6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.092Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.118Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.143Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.164Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.454Z: 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 20, 2022 1:00:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.520Z: Starting 5 ****s in us-central1-b... Apr 20, 2022 1:01:12 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:01:10.586Z: 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 20, 2022 1:01:37 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:01:37.202Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s). Apr 20, 2022 1:01:43 PM org.apache.beam.runners.dataflow.DataflowPipelineJob lambda$waitUntilFinish$0 WARNING: Job is already running in Google Cloud Platform, Ctrl-C will not cancel it. To cancel the job in the cloud, run: > gcloud dataflow jobs --project=apache-beam-testing cancel > --region=us-central1 2022-04-20_06_00_47-9508044923897138893 > 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=2ae10975-431e-4d19-bd5e-73a3a0cfc811, currentDir=<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java17/ws/src}> Attempting to read last messages from the daemon log... Daemon pid: 3373938 log file: /home/jenkins/.gradle/daemon/7.4/daemon-3373938.out.log ----- Last 20 lines from daemon log file - daemon-3373938.out.log ----- INFO: 2022-04-20T13:00:56.092Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.118Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.143Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.164Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation) Apr 20, 2022 1:00:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.454Z: 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 20, 2022 1:00:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:00:56.520Z: Starting 5 ****s in us-central1-b... Apr 20, 2022 1:01:12 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:01:10.586Z: 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 20, 2022 1:01:37 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-04-20T13:01:37.202Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s). Apr 20, 2022 1:01:43 PM org.apache.beam.runners.dataflow.DataflowPipelineJob lambda$waitUntilFinish$0 WARNING: Job is already running in Google Cloud Platform, Ctrl-C will not cancel it. To cancel the job in the cloud, run: > gcloud dataflow jobs --project=apache-beam-testing cancel > --region=us-central1 2022-04-20_06_00_47-9508044923897138893 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 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]
