See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/404/display/redirect?page=changes>
Changes: [chamikaramj] Remove unnecessary reference to use_runner_v2 experiment in x-lang [bulat.safiullin] [Website] remove beam-summit 2022 container with all related files [yixiaoshen] Fix typo in Datastore V1ReadIT test [noreply] Add read/write PubSub integration example fhirio pipeline (#22306) [noreply] Remove deprecated Session runner (#22505) [noreply] Add Go test status to the PR template (#22508) [noreply] Relax the google-api-core dependency. (#22513) ------------------------------------------ [...truncated 47.05 KB...] 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 :release:go-licenses:java:createLicenses > Task :sdks:java:container:java11:copyGolangLicenses > 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] 3ff58e3bc952: Preparing ea498dc0ed69: Preparing 04919d89a2fc: Preparing 14c62dbe8ee8: Preparing a9f21b42653d: Preparing 09e99fb792bd: Preparing 29845b694233: Preparing 261fa9184a64: Preparing 7789fe38c36d: Preparing 93e2b869f3b8: Preparing 3cd1f45f85dd: Preparing 0a34f502c005: Preparing 2a3d138cd2a9: Preparing 14dc44613df3: Preparing 622e5c1e04f2: Preparing d638d10edc43: Preparing 2f1e2f8ca577: Preparing 4dc3dda529a0: Preparing 7372faf8e603: Preparing 9be7f4e74e71: Preparing 36cd374265f4: Preparing 5bdeef4a08f3: Preparing 14dc44613df3: Waiting 09e99fb792bd: Waiting 622e5c1e04f2: Waiting 7372faf8e603: Waiting 9be7f4e74e71: Waiting 4dc3dda529a0: Waiting d638d10edc43: Waiting 29845b694233: Waiting 2f1e2f8ca577: Waiting 0a34f502c005: Waiting 93e2b869f3b8: Waiting 5bdeef4a08f3: Waiting 3cd1f45f85dd: Waiting 7789fe38c36d: Waiting 2a3d138cd2a9: Waiting ea498dc0ed69: Pushed 14c62dbe8ee8: Pushed a9f21b42653d: Pushed 04919d89a2fc: Pushed 3ff58e3bc952: Pushed 261fa9184a64: Pushed 29845b694233: Pushed 93e2b869f3b8: Pushed 7789fe38c36d: Pushed 0a34f502c005: Pushed 09e99fb792bd: Pushed d638d10edc43: Layer already exists 2f1e2f8ca577: Layer already exists 4dc3dda529a0: Layer already exists 7372faf8e603: Layer already exists 3cd1f45f85dd: Pushed 9be7f4e74e71: Layer already exists 5bdeef4a08f3: Layer already exists 36cd374265f4: Layer already exists 14dc44613df3: Pushed 622e5c1e04f2: Pushed 2a3d138cd2a9: Pushed 20220729124130: digest: sha256:b1970e05972f185ab73bbcef42c010707ed3405e25a36f8a5a98963a6dfd2615 size: 4935 > Task :sdks:java:testing:load-tests:run Jul 29, 2022 12:42:36 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create INFO: No stagingLocation provided, falling back to gcpTempLocation Jul 29, 2022 12:42:37 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 29, 2022 12:42:38 PM org.apache.beam.sdk.Pipeline validate WARNING: The following transforms do not have stable unique names: ParDo(TimeMonitor) Jul 29, 2022 12:42:38 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 29, 2022 12:42:40 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location to prepare for execution. Jul 29, 2022 12:42:41 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 0 seconds Jul 29, 2022 12:42:41 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/ Jul 29, 2022 12:42:41 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage INFO: Uploading <112521 bytes, hash 580bc8877ba8c3f742108aaa14a25e1061929608ee853f7930579f8fdfe775fb> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-WAvIh3uow_dCEIqqFKJeEGGSlgjuhT95MFefj9_ndfs.pb Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input as step s1 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor) as step s2 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(ByteMonitor) as step s3 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 0 as step s4 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 1 as step s5 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 2 as step s6 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 3 as step s7 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 4 as step s8 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 5 as step s9 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 6 as step s10 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 7 as step s11 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 8 as step s12 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Step: 9 as step s13 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding ParDo(TimeMonitor)2 as step s14 Jul 29, 2022 12:42:43 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Dataflow SDK version: 2.42.0-SNAPSHOT Jul 29, 2022 12:42:44 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-29_05_42_43-2047715209359424360?project=apache-beam-testing Jul 29, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Submitted job: 2022-07-29_05_42_43-2047715209359424360 Jul 29, 2022 12:42:44 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-29_05_42_43-2047715209359424360 Jul 29, 2022 12:42:52 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2022-07-29T12:42:49.774Z: 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-072912-qidl. 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 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:55.043Z: Worker configuration: e2-standard-2 in us-central1-b. Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:55.830Z: Expanding SplittableParDo operations into optimizable parts. Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:55.887Z: Expanding CollectionToSingleton operations into optimizable parts. Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:55.954Z: Expanding CoGroupByKey operations into optimizable parts. Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:55.996Z: Expanding GroupByKey operations into optimizable parts. Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.063Z: Fusing adjacent ParDo, Read, Write, and Flatten operations Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.101Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.127Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.163Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction Jul 29, 2022 12:42:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.195Z: Fusing consumer ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.229Z: Fusing consumer ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.262Z: Fusing consumer Step: 0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.293Z: Fusing consumer Step: 1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.319Z: Fusing consumer Step: 2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.345Z: Fusing consumer Step: 3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.370Z: Fusing consumer Step: 4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.403Z: Fusing consumer Step: 5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.442Z: Fusing consumer Step: 6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.480Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.504Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.526Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.558Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation) Jul 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:56.931Z: 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 29, 2022 12:42:58 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:42:57.008Z: Starting 5 ****s in us-central1-b... Jul 29, 2022 12:43:26 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:43:25.892Z: 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 29, 2022 12:43:36 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:43:35.403Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s). Jul 29, 2022 12:44:28 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:44:28.505Z: 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=544ef934-5ab2-456c-aef7-42b1538eeb39, 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: 1980887 log file: /home/jenkins/.gradle/daemon/7.4/daemon-1980887.out.log ----- Last 20 lines from daemon log file - daemon-1980887.out.log ----- Jul 29, 2022 12:44:28 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2022-07-29T12:44:28.505Z: Workers have started successfully. Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220729124130 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:b1970e05972f185ab73bbcef42c010707ed3405e25a36f8a5a98963a6dfd2615 Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. Remove shutdown hook failed java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) at java.lang.Runtime.removeShutdownHook(Runtime.java:239) at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:38) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) at org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ----- 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:20220729124130 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:b1970e05972f185ab73bbcef42c010707ed3405e25a36f8a5a98963a6dfd2615 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]
