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

Changes:

[noreply] fix minor unreachable code caused by log.Fatal (#22618)


------------------------------------------
[...truncated 43.25 KB...]
> Task :sdks:java:container:pullLicenses
INFO:root:Pulling license for 241 dependencies using 16 threads.
INFO:root:Replaced local file URL with 
file://<https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/ws/src/sdks/java/container/license_scripts/manual_licenses/xz/COPYING>
 for xz-1.5
INFO:root:pull_licenses_java.py succeed. It took 9.155453 seconds with 16 
threads.

> 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 :release:go-licenses:java:createLicenses

> 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: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]
f97c62dfac18: Preparing
e80e5cec68f9: Preparing
235e9a3834da: Preparing
a5eefca62113: Preparing
02988f7f9cfb: Preparing
4aad1522f532: Preparing
4edba4576c34: Preparing
4b270f935056: Preparing
c52cc77380da: Preparing
facf554f627d: Preparing
888552b53ea1: Preparing
07b317268f5c: Preparing
c6cb76ef9f6d: Preparing
27101088fda6: Preparing
9651c8a5c4ad: Preparing
7b7f3078e1db: Preparing
826c3ddbb29c: Preparing
b626401ef603: Preparing
4aad1522f532: Waiting
9b55156abf26: Preparing
293d5db30c9f: Preparing
4b270f935056: Waiting
03127cdb479b: Preparing
4edba4576c34: Waiting
9c742cd6c7a5: Preparing
c52cc77380da: Waiting
facf554f627d: Waiting
c6cb76ef9f6d: Waiting
888552b53ea1: Waiting
9b55156abf26: Waiting
27101088fda6: Waiting
07b317268f5c: Waiting
826c3ddbb29c: Waiting
293d5db30c9f: Waiting
9651c8a5c4ad: Waiting
b626401ef603: Waiting
9c742cd6c7a5: Waiting
7b7f3078e1db: Waiting
e80e5cec68f9: Pushed
02988f7f9cfb: Pushed
a5eefca62113: Pushed
235e9a3834da: Pushed
f97c62dfac18: Pushed
4edba4576c34: Pushed
4b270f935056: Pushed
facf554f627d: Pushed
07b317268f5c: Pushed
c52cc77380da: Pushed
4aad1522f532: Pushed
7b7f3078e1db: Layer already exists
826c3ddbb29c: Layer already exists
b626401ef603: Layer already exists
888552b53ea1: Pushed
293d5db30c9f: Layer already exists
03127cdb479b: Layer already exists
9b55156abf26: Layer already exists
9c742cd6c7a5: Layer already exists
27101088fda6: Pushed
9651c8a5c4ad: Pushed
c6cb76ef9f6d: Pushed
20220815124130: digest: 
sha256:2005243ec5cbe4e6ee7a9e930ffbde431bd9e480ce1921b94aa6d58552ff4d69 size: 
4935

> Task :sdks:java:testing:load-tests:run
Aug 15, 2022 12:42:39 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Aug 15, 2022 12:42:39 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.
Aug 15, 2022 12:42:40 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: 
ParDo(TimeMonitor)
Aug 15, 2022 12:42:40 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.
Aug 15, 2022 12:42:43 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 222 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Aug 15, 2022 12:42:44 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 222 files cached, 0 files newly uploaded in 0 
seconds
Aug 15, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Aug 15, 2022 12:42:44 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <112521 bytes, hash 
ecf158d534580edf2c7e38e1b428dcecf0a5bcae1050c6e7d88079624fe53e78> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-7PFY1TRYDt8sfjjhtCjc7PClvK4QUMbn2IB5Yk_lPng.pb
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 1 as step s5
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 2 as step s6
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 3 as step s7
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 4 as step s8
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 5 as step s9
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 6 as step s10
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 7 as step s11
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 8 as step s12
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 9 as step s13
Aug 15, 2022 12:42:46 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s14
Aug 15, 2022 12:42:46 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.42.0-SNAPSHOT
Aug 15, 2022 12:42:46 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-08-15_05_42_46-9530636021809844280?project=apache-beam-testing
Aug 15, 2022 12:42:46 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-08-15_05_42_46-9530636021809844280
Aug 15, 2022 12:42:46 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-08-15_05_42_46-9530636021809844280
Aug 15, 2022 12:42:50 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-08-15T12:42:49.048Z: 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-081512-crs9. 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
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:56.013Z: Worker configuration: e2-standard-2 in 
us-central1-a.
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:56.943Z: Expanding SplittableParDo operations into 
optimizable parts.
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:56.977Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.035Z: Expanding CoGroupByKey operations into 
optimizable parts.
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.078Z: Expanding GroupByKey operations into 
optimizable parts.
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.189Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.226Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.252Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.275Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.314Z: Fusing consumer 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.343Z: Fusing consumer 
ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.370Z: Fusing consumer Step: 
0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.393Z: Fusing consumer Step: 
1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.430Z: Fusing consumer Step: 
2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.468Z: Fusing consumer Step: 
3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.495Z: Fusing consumer Step: 
4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.531Z: Fusing consumer Step: 
5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.568Z: Fusing consumer Step: 
6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.595Z: Fusing consumer Step: 
7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.623Z: Fusing consumer Step: 
8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.657Z: Fusing consumer Step: 
9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:57.686Z: Fusing consumer 
ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 
9/ParMultiDo(CounterOperation)
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:58.057Z: 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
Aug 15, 2022 12:42:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:42:58.175Z: Starting 5 ****s in us-central1-a...
Aug 15, 2022 12:43:24 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:43:19.051Z: 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
Aug 15, 2022 12:43:36 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:43:33.035Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).

> 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=7bdcd0a9-1c04-4f3f-af35-049db51027f8, 
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: 4130735
  log file: /home/jenkins/.gradle/daemon/7.4/daemon-4130735.out.log
----- Last  20 lines from daemon log file - daemon-4130735.out.log -----
Aug 15, 2022 12:43:24 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:43:19.051Z: 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
Aug 15, 2022 12:43:36 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-08-15T12:43:33.035Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
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:750)
----- 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]

Reply via email to