See <https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Batch_Java17/379/display/redirect>
Changes: ------------------------------------------ [...truncated 48.82 KB...] > Task :sdks:java:container:java17:copySdkHarnessLauncher Execution optimizations have been disabled for task ':sdks:java:container:java17: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_GBK_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: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.5.1/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_GBK_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.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. > 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] b2a4cdd87a58: Preparing c5a6ffacf07e: Preparing e246935c21d8: Preparing c6f3e91876a9: Preparing 65dca7287a35: Preparing 738998ce4bac: Preparing 4913cb5813a6: Preparing a798478b9b57: Preparing 925b8b21a9bd: Preparing a21be73daf3b: Preparing 2b6f77d26339: Preparing 8aef38c3723b: Preparing 667aad63447d: Preparing f5d4044821dd: Preparing 95e5467cb506: Preparing 3bc383470c05: Preparing e93827457889: Preparing 08fa02ce37eb: Preparing a037458de4e0: Preparing bafdbe68e4ae: Preparing 925b8b21a9bd: Waiting a13c519c6361: Preparing a21be73daf3b: Waiting 2b6f77d26339: Waiting e93827457889: Waiting 8aef38c3723b: Waiting 08fa02ce37eb: Waiting a037458de4e0: Waiting 95e5467cb506: Waiting 667aad63447d: Waiting 3bc383470c05: Waiting bafdbe68e4ae: Waiting f5d4044821dd: Waiting a13c519c6361: Waiting 738998ce4bac: Waiting 4913cb5813a6: Waiting a798478b9b57: Waiting e246935c21d8: Pushed c6f3e91876a9: Pushed c5a6ffacf07e: Pushed 65dca7287a35: Pushed b2a4cdd87a58: Pushed 4913cb5813a6: Pushed a798478b9b57: Pushed a21be73daf3b: Pushed 925b8b21a9bd: Pushed 8aef38c3723b: Pushed 738998ce4bac: Pushed 2b6f77d26339: 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 667aad63447d: Pushed f5d4044821dd: Pushed 95e5467cb506: Pushed 20230102144450: digest: sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c size: 4728 > Task :sdks:java:testing:load-tests:run Jan 02, 2023 2:45:59 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create INFO: No stagingLocation provided, falling back to gcpTempLocation Jan 02, 2023 2:46:00 PM 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. Jan 02, 2023 2:46:01 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. Jan 02, 2023 2:46:03 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Uploading 232 files from PipelineOptions.filesToStage to staging location to prepare for execution. Jan 02, 2023 2:46:03 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Staging files complete: 232 files cached, 0 files newly uploaded in 0 seconds Jan 02, 2023 2:46:03 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/ Jan 02, 2023 2:46:03 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage INFO: Uploading <98459 bytes, hash 52b5edc5ca6024cc343c614b794e2a7e94418398972d68531f157e1de6f88c16> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-UrXtxcpgJMw0PGFLeU4qfpRBg5iXLWhTHxV-Heb4jBY.pb Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input as step s1 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Collect start time metrics as step s2 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Total bytes monitor as step s3 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Window.Into()/Window.Assign as step s4 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Group by key (0) as step s5 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Ungroup and reiterate (0) as step s6 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Collect end time metrics (0) as step s7 Jan 02, 2023 2:46:05 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Dataflow SDK version: 2.45.0-SNAPSHOT Jan 02, 2023 2:46:06 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/2023-01-02_06_46_05-18351850487485667374?project=apache-beam-testing Jan 02, 2023 2:46:06 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Submitted job: 2023-01-02_06_46_05-18351850487485667374 Jan 02, 2023 2:46:06 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 2023-01-02_06_46_05-18351850487485667374 Jan 02, 2023 2:46:10 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2023-01-02T14:46:09.362Z: 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: load0tests0java170dataflow0v20batch0gbk01-jenkins-01021446-axe0. 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 Jan 02, 2023 2:46:16 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:15.880Z: Worker configuration: e2-standard-2 in us-central1-f. Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:16.957Z: Expanding SplittableParDo operations into optimizable parts. Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:16.987Z: Expanding CollectionToSingleton operations into optimizable parts. Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.042Z: Expanding CoGroupByKey operations into optimizable parts. Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.093Z: Expanding GroupByKey operations into optimizable parts. Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.161Z: Fusing adjacent ParDo, Read, Write, and Flatten operations Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.198Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.237Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.270Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.302Z: Fusing consumer Collect start time metrics/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.333Z: Fusing consumer Total bytes monitor/ParMultiDo(ByteMonitor) into Collect start time metrics/ParMultiDo(TimeMonitor) Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.368Z: Fusing consumer Window.Into()/Window.Assign into Total bytes monitor/ParMultiDo(ByteMonitor) Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.412Z: Fusing consumer Group by key (0)/Write into Window.Into()/Window.Assign Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.451Z: Fusing consumer Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate) into Group by key (0)/Read Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.487Z: Fusing consumer Collect end time metrics (0)/ParMultiDo(TimeMonitor) into Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate) Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.821Z: 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 Jan 02, 2023 2:46:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:17.893Z: Starting 5 ****s in us-central1-f... Jan 02, 2023 2:46:27 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:46:25.507Z: 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 Jan 02, 2023 2:47:01 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:47:00.341Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s). Jan 02, 2023 2:48:09 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:08.760Z: Workers have started successfully. Jan 02, 2023 2:48:25 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:24.546Z: All ****s have finished the startup processes and began to receive work requests. Jan 02, 2023 2:48:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:27.988Z: 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 Jan 02, 2023 2:48:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:28.139Z: Executing operation Group by key (0)/Create Jan 02, 2023 2:48:30 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:29.507Z: Finished operation Group by key (0)/Create Jan 02, 2023 2:48:30 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:48:29.643Z: 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 Jan 02, 2023 2:49:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:49:26.918Z: 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 Jan 02, 2023 2:49:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:49:26.998Z: Executing operation Group by key (0)/Close Jan 02, 2023 2:49:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:49:27.316Z: Finished operation Group by key (0)/Close Jan 02, 2023 2:49:29 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:49:27.384Z: Executing operation Group by key (0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end time metrics (0)/ParMultiDo(TimeMonitor) Jan 02, 2023 2:50:05 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:50:04.169Z: Finished operation Group by key (0)/Read+Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate)+Collect end time metrics (0)/ParMultiDo(TimeMonitor) Jan 02, 2023 2:50:05 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:50:04.347Z: Cleaning up. Jan 02, 2023 2:50:05 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:50:04.439Z: Stopping **** pool... Jan 02, 2023 2:52:19 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:52:17.639Z: Autoscaling: Resized **** pool from 5 to 0. Jan 02, 2023 2:52:19 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-01-02T14:52:17.686Z: Worker pool stopped. Jan 02, 2023 2:52:23 PM org.apache.beam.runners.dataflow.DataflowPipelineJob logTerminalState INFO: Job 2023-01-02_06_46_05-18351850487485667374 finished with status DONE. Load test results for test (ID): 87ce84ba-85cc-42ce-927a-b9ccff97af92 and timestamp: 2023-01-02T14:46:00.844000000Z: Metric: Value: dataflow_v2_java17_runtime_sec 90.998 dataflow_v2_java17_total_bytes_count 2.0E9 > Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230102144450 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c WARNING: Successfully resolved tag to sha256, but it is recommended to use sha256 directly. Tag: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230102144450] - referencing digest: [us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c] Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230102144450] (referencing [us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c])]. Removing untagged image us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c Digests: - us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c Deleted [us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:4ee5a2dbe8c5f34b06d576750c97e4091c386d49fa8b0eeec9a5c478f5e73c1c]. Removing untagged image us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:80f8d07d62b3eb300a9dc1bc319d9489957bee5ea466e0b6d599042b6c128293 Digests: - us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:80f8d07d62b3eb300a9dc1bc319d9489957bee5ea466e0b6d599042b6c128293 ERROR: (gcloud.container.images.delete) Not found: response: {'docker-distribution-api-version': 'registry/2.0', 'content-type': 'application/json', 'content-encoding': 'gzip', 'date': 'Mon, 02 Jan 2023 14:52:30 GMT', 'server': 'Docker Registry', 'cache-control': 'private', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'transfer-encoding': 'chunked', 'status': 404} Failed to compute blob liveness for manifest: 'sha256:80f8d07d62b3eb300a9dc1bc319d9489957bee5ea466e0b6d599042b6c128293': None > 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_Java17/ws/src/runners/google-cloud-dataflow-java/build.gradle'> line: 305 * What went wrong: Execution failed for task ':runners:google-cloud-dataflow-java:cleanUpDockerJavaImages'. > Process 'command './scripts/cleanup_untagged_gcr_images.sh'' 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 7m 55s 113 actionable tasks: 75 executed, 34 from cache, 4 up-to-date Publishing build scan... https://gradle.com/s/rzm7dbipc4vxo 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]
