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/10/12 12:44:38 UTC
Build failed in Jenkins: beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11 #479
See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/479/display/redirect?page=changes>
Changes:
[git] BEAM-13592 Add getOrderingKey in
[git] Add CHANGES entry
[git] Rename transform name according to review comment
[git] Update to pass ordering key
[egalpin] Adds ordering key to OutgoingMessage builder, adds new coders to pubsub
[egalpin] Fixes pubsub bounded writer allowing for orderingKey
[egalpin] Alters order of pubsub message support in registrar
[egalpin] Removed publishTime and messageId in grpc pubsub client publish
[egalpin] Attempts to allow different pubsub root url for PubsubIO.Write
[egalpin] Fixes pubsub tests root url
[egalpin] Puts PubsubMessageCoder last in registrar
[egalpin] Uses MoreObjects over Objects
[egalpin] Renames PubsubMessageCoder to
[Robert Bradshaw] Add a multi-process shared utility.
[Robert Bradshaw] Add fastener dependency.
[Robert Bradshaw] Refactor to have an explicit acquire/release API.
[Robert Bradshaw] Drop a TODO about deferred construction parameterization.
[Robert Bradshaw] Fix unused import/var.
[Moritz Mack] Replace website references to deprecated aws / kinesis modules with more
[noreply] fix distribution example in golang guide (#23567)
[Alexey Romanenko] [website][adhoc] Fix spellcheck errors and typos
[noreply] Add database role to SpannerConfig for role-based access control.
[noreply] Remove obsolete and deprecated bigquery native read. (#23557)
[noreply] Feature/name all java threads (#23387)
[noreply] [Go SDK] Don't construct plans in lock section. (#23583)
[noreply] Remove obsolete and deprecated bigquery native write. #23557 (#23558)
[noreply] Increase Python PostCommit timeout. (#23595)
------------------------------------------
[...truncated 47.64 KB...]
> 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.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_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.5.1/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]
619ad19de38a: Preparing
0e8ea4060164: Preparing
a8f172b5c395: Preparing
3b967b595deb: Preparing
c1b79cab049b: Preparing
87dc016a109c: Preparing
4c1ac39051cd: Preparing
2ab505fabc31: Preparing
5acdf08fd5e5: Preparing
95b0e59ec24a: Preparing
3e978ffdbfc2: Preparing
341db4239726: Preparing
e9102a4e7118: Preparing
525589ef62cb: Preparing
887684298b1d: Preparing
7b7f3078e1db: Preparing
826c3ddbb29c: Preparing
b626401ef603: Preparing
9b55156abf26: Preparing
293d5db30c9f: Preparing
03127cdb479b: Preparing
9c742cd6c7a5: Preparing
525589ef62cb: Waiting
9b55156abf26: Waiting
887684298b1d: Waiting
293d5db30c9f: Waiting
7b7f3078e1db: Waiting
4c1ac39051cd: Waiting
03127cdb479b: Waiting
826c3ddbb29c: Waiting
2ab505fabc31: Waiting
9c742cd6c7a5: Waiting
87dc016a109c: Waiting
5acdf08fd5e5: Waiting
b626401ef603: Waiting
341db4239726: Waiting
e9102a4e7118: Waiting
3e978ffdbfc2: Waiting
95b0e59ec24a: Waiting
c1b79cab049b: Pushed
3b967b595deb: Pushed
a8f172b5c395: Pushed
0e8ea4060164: Pushed
619ad19de38a: Pushed
4c1ac39051cd: Pushed
2ab505fabc31: Pushed
95b0e59ec24a: Pushed
341db4239726: Pushed
87dc016a109c: Pushed
3e978ffdbfc2: Pushed
7b7f3078e1db: Layer already exists
826c3ddbb29c: Layer already exists
b626401ef603: Layer already exists
9b55156abf26: Layer already exists
293d5db30c9f: Layer already exists
03127cdb479b: Layer already exists
9c742cd6c7a5: Layer already exists
887684298b1d: Pushed
525589ef62cb: Pushed
5acdf08fd5e5: Pushed
e9102a4e7118: Pushed
20221012124133: digest: sha256:318e6d06f32d7c4a4107930be4ae677a613af725424cbefb4a619c4892da14ab size: 4935
> Task :sdks:java:testing:load-tests:run
Oct 12, 2022 12:42:38 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Oct 12, 2022 12:42:38 PM org.apache.beam.runners.dataflow.DataflowRunner fromOptions
INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from the classpath: will stage 229 files. Enable logging at DEBUG level to see which files will be staged.
Oct 12, 2022 12:42:39 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: ParDo(TimeMonitor)
Oct 12, 2022 12:42:39 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.
Oct 12, 2022 12:42:42 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements
INFO: Uploading 229 files from PipelineOptions.filesToStage to staging location to prepare for execution.
Oct 12, 2022 12:42:42 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements
INFO: Staging files complete: 229 files cached, 0 files newly uploaded in 0 seconds
Oct 12, 2022 12:42:42 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/
Oct 12, 2022 12:42:42 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage
INFO: Uploading <114866 bytes, hash f8f63373c9f22d11780f4b0813eb427e7b9cea242c96c5ca87e6e8763267c955> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline--PYzc8nyLRF4D0sIE-tCfnuc6iQslsXKh-bodjJnyVU.pb
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 1 as step s5
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 2 as step s6
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 3 as step s7
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 4 as step s8
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 5 as step s9
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 6 as step s10
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 7 as step s11
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 8 as step s12
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 9 as step s13
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s14
Oct 12, 2022 12:42:44 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.43.0-SNAPSHOT
Oct 12, 2022 12:42:45 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-10-12_05_42_44-7780931449240547377?project=apache-beam-testing
Oct 12, 2022 12:42:45 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-10-12_05_42_44-7780931449240547377
Oct 12, 2022 12:42:45 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-10-12_05_42_44-7780931449240547377
Oct 12, 2022 12:42:48 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-10-12T12:42:48.040Z: 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-101212-uwlk. 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
Oct 12, 2022 12:42:55 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:54.742Z: Worker configuration: e2-standard-2 in us-central1-b.
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.020Z: Expanding SplittableParDo operations into optimizable parts.
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.043Z: Expanding CollectionToSingleton operations into optimizable parts.
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.108Z: Expanding CoGroupByKey operations into optimizable parts.
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.145Z: Expanding GroupByKey operations into optimizable parts.
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.215Z: Fusing adjacent ParDo, Read, Write, and Flatten operations
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.246Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.278Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.311Z: Fusing consumer Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.343Z: Fusing consumer ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.377Z: Fusing consumer ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.411Z: Fusing consumer Step: 0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.445Z: Fusing consumer Step: 1/ParMultiDo(CounterOperation) into Step: 0/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.480Z: Fusing consumer Step: 2/ParMultiDo(CounterOperation) into Step: 1/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.508Z: Fusing consumer Step: 3/ParMultiDo(CounterOperation) into Step: 2/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.535Z: Fusing consumer Step: 4/ParMultiDo(CounterOperation) into Step: 3/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.572Z: Fusing consumer Step: 5/ParMultiDo(CounterOperation) into Step: 4/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.603Z: Fusing consumer Step: 6/ParMultiDo(CounterOperation) into Step: 5/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.641Z: Fusing consumer Step: 7/ParMultiDo(CounterOperation) into Step: 6/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.663Z: Fusing consumer Step: 8/ParMultiDo(CounterOperation) into Step: 7/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.685Z: Fusing consumer Step: 9/ParMultiDo(CounterOperation) into Step: 8/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:56.722Z: Fusing consumer ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 9/ParMultiDo(CounterOperation)
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:57.047Z: 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
Oct 12, 2022 12:42:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:42:57.134Z: Starting 5 ****s in us-central1-b...
Oct 12, 2022 12:43:16 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:43:14.227Z: 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
Oct 12, 2022 12:43:40 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-10-12T12:43:39.187Z: Autoscaling: Raised the number of ****s to 5 based on the rate of progress in the currently running stage(s).
Oct 12, 2022 12:44:37 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-10-12_05_42_44-7780931449240547377
> 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=23ae881a-ad61-4423-ad12-f65d57aecf90, 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: 141402
log file: /home/jenkins/.gradle/daemon/7.5.1/daemon-141402.out.log
----- Last 20 lines from daemon log file - daemon-141402.out.log -----
To cancel the job in the cloud, run:
> gcloud dataflow jobs --project=apache-beam-testing cancel --region=us-central1 2022-10-12_05_42_44-7780931449240547377
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20221012124133
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:318e6d06f32d7c4a4107930be4ae677a613af725424cbefb4a619c4892da14ab
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:366)
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
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20221012124133
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:318e6d06f32d7c4a4107930be4ae677a613af725424cbefb4a619c4892da14ab
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 #480
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_V2_Batch_Java11/480/display/redirect?page=changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org