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

Changes:

[benjamin.gonzalez] [BEAM-8970] Add docs to run wordcount example on portable 
Spark Runner

[Kiley Sok] Update python container version

[benjamin.gonzalez] [BEAM-8970] Add period to end of sentence

[Kyle Weaver] Add self-descriptive message for expected errors.

[noreply] Add --dataflowServiceOptions=enable_prime to useUnifiedWorker 
conditions

[noreply] [BEAM-10529] nullable xlang coder (#16923)

[noreply] Fix go fmt break in core/typex/special.go (#17266)

[noreply] [BEAM-5436] Add doc page on Go cross compilation. (#17256)

[noreply] Pr-bot Don't count all reviews as approvals (#17269)

[noreply] Fix postcommits (#17263)

[noreply] [BEAM-14241] Address staticcheck warnings in boot.go (#17264)

[noreply] [BEAM-14157] GrpcWindmillServer: Use stream specific boolean to do

[noreply] [BEAM-10582] Allow (and test) pyarrow 7 (#17229)

[noreply] [BEAM-13519] Solve race issues when the server responds with an error


------------------------------------------
[...truncated 243.79 KB...]
> Task :runners:java-fn-execution:jar UP-TO-DATE
> Task :sdks:java:harness:shadowJar UP-TO-DATE
> Task :sdks:java:expansion-service:compileJava UP-TO-DATE
> Task :sdks:java:expansion-service:classes UP-TO-DATE
> Task :sdks:java:expansion-service:jar UP-TO-DATE
> Task :sdks:java:io:kafka:compileJava UP-TO-DATE
> Task :sdks:java:io:kafka:classes UP-TO-DATE
> Task :sdks:java:io:kafka:jar UP-TO-DATE
> Task :sdks:java:container:java17:copyDockerfileDependencies UP-TO-DATE
> Task :sdks:java:io:google-cloud-platform:compileJava UP-TO-DATE
> Task :sdks:java:io:google-cloud-platform:classes UP-TO-DATE
> Task :sdks:java:io:google-cloud-platform:jar UP-TO-DATE
> Task :sdks:java:testing:load-tests:compileJava UP-TO-DATE
> Task :sdks:java:testing:load-tests:classes UP-TO-DATE
> Task :sdks:java:testing:load-tests:jar UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:compileJava UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:classes UP-TO-DATE
> Task :runners:google-cloud-dataflow-java:jar UP-TO-DATE

> Task :sdks:java:container:goBuild
/home/jenkins/go/bin/go1.16.12 build -o ./build/target/linux_amd64/boot boot.go

> 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_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: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.3.2/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_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.3.2/userguide/validation_problems.html#implicit_dependency
 for more details about this problem.

> 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]
503052bcbe6d: Preparing
84e0653f4540: Preparing
f47fe6df78ca: Preparing
e23035313282: Preparing
a9a9dc3bd9f7: Preparing
003a90c3a68e: Preparing
126ec60f7f49: Preparing
9cb78d29ba80: Preparing
4749609026bf: Preparing
338226609a40: Preparing
5a1a991dd36e: Preparing
cbac6d86a640: Preparing
d4e47e392493: Preparing
41d1c3469f3b: Preparing
7b40cd33d775: Preparing
a0cd5c3af747: Preparing
62a2af0b61ef: Preparing
7a7698da17f2: Preparing
d59769727d80: Preparing
348622fdcc61: Preparing
4ac8bc2cd0be: Preparing
9cb78d29ba80: Waiting
338226609a40: Waiting
5a1a991dd36e: Waiting
7b40cd33d775: Waiting
d59769727d80: Waiting
4749609026bf: Waiting
a0cd5c3af747: Waiting
41d1c3469f3b: Waiting
003a90c3a68e: Waiting
cbac6d86a640: Waiting
d4e47e392493: Waiting
7a7698da17f2: Waiting
4ac8bc2cd0be: Waiting
348622fdcc61: Waiting
62a2af0b61ef: Waiting
126ec60f7f49: Waiting
e23035313282: Pushed
a9a9dc3bd9f7: Pushed
f47fe6df78ca: Pushed
84e0653f4540: Pushed
503052bcbe6d: Pushed
126ec60f7f49: Pushed
9cb78d29ba80: Pushed
003a90c3a68e: Pushed
338226609a40: Pushed
4749609026bf: Pushed
cbac6d86a640: Pushed
a0cd5c3af747: Layer already exists
5a1a991dd36e: Pushed
62a2af0b61ef: Layer already exists
7a7698da17f2: Layer already exists
d59769727d80: Layer already exists
348622fdcc61: Layer already exists
4ac8bc2cd0be: Layer already exists
41d1c3469f3b: Pushed
7b40cd33d775: Pushed
d4e47e392493: Pushed
20220405131117: digest: 
sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf size: 
4729

> Task :sdks:java:testing:load-tests:run
Apr 05, 2022 1:11:50 PM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
INFO: No stagingLocation provided, falling back to gcpTempLocation
Apr 05, 2022 1:11:50 PM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from 
the classpath: will stage 207 files. Enable logging at DEBUG level to see which 
files will be staged.
Apr 05, 2022 1:11:51 PM org.apache.beam.sdk.Pipeline validate
WARNING: The following transforms do not have stable unique names: 
ParDo(TimeMonitor)
Apr 05, 2022 1:11:51 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 05, 2022 1:11:53 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Uploading 207 files from PipelineOptions.filesToStage to staging location 
to prepare for execution.
Apr 05, 2022 1:11:54 PM org.apache.beam.runners.dataflow.util.PackageUtil 
stageClasspathElements
INFO: Staging files complete: 207 files cached, 0 files newly uploaded in 0 
seconds
Apr 05, 2022 1:11:54 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Staging portable pipeline proto to 
gs://temp-storage-for-perf-tests/loadtests/staging/
Apr 05, 2022 1:11:54 PM org.apache.beam.runners.dataflow.util.PackageUtil 
tryStagePackage
INFO: Uploading <88121 bytes, hash 
3b63ef19d9fa36ec4fd97ea16143a1e77e117d29d6ac86fc5206641d5e1ce904> to 
gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-O2PvGdn6NuxP2X6hYUOh534RfSnWrIb8UgZkHV4c6QQ.pb
Apr 05, 2022 1:11:55 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Read input as step s1
Apr 05, 2022 1:11:55 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor) as step s2
Apr 05, 2022 1:11:56 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(ByteMonitor) as step s3
Apr 05, 2022 1:11:56 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding Step: 0 as step s4
Apr 05, 2022 1:11:56 PM 
org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep
INFO: Adding ParDo(TimeMonitor)2 as step s5
Apr 05, 2022 1:11:56 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Dataflow SDK version: 2.39.0-SNAPSHOT
Apr 05, 2022 1:11:56 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-05_06_11_56-5811193247178506521?project=apache-beam-testing
Apr 05, 2022 1:11:56 PM org.apache.beam.runners.dataflow.DataflowRunner run
INFO: Submitted job: 2022-04-05_06_11_56-5811193247178506521
Apr 05, 2022 1:11:56 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-05_06_11_56-5811193247178506521
Apr 05, 2022 1:12:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
WARNING: 2022-04-05T13:11:59.093Z: 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: 
load0tests0java170dataflow0v20batch0pardo03-jenkins-040513-arhh. 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 05, 2022 1:12:05 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:05.443Z: Worker configuration: e2-standard-2 in 
us-central1-b.
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.138Z: Expanding SplittableParDo operations into 
optimizable parts.
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.163Z: Expanding CollectionToSingleton operations into 
optimizable parts.
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.218Z: Expanding CoGroupByKey operations into 
optimizable parts.
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.257Z: Expanding GroupByKey operations into 
optimizable parts.
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.320Z: Fusing adjacent ParDo, Read, Write, and Flatten 
operations
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.354Z: Fusing consumer Read 
input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read 
input/Impulse
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.385Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
 into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource)
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.417Z: Fusing consumer 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/SplitWithSizing
 into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/PairWithRestriction
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.441Z: Fusing consumer 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor) into 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.475Z: Fusing consumer 
ParDo(ByteMonitor)/ParMultiDo(ByteMonitor) into 
ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.509Z: Fusing consumer Step: 
0/ParMultiDo(CounterOperation) into ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:06.542Z: Fusing consumer 
ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor) into Step: 
0/ParMultiDo(CounterOperation)
Apr 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:07.003Z: 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 05, 2022 1:12:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:07.096Z: Starting 5 ****s in us-central1-b...
Apr 05, 2022 1:12:32 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:31.260Z: 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 05, 2022 1:12:48 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:12:47.303Z: Autoscaling: Raised the number of ****s to 5 
based on the rate of progress in the currently running stage(s).
Apr 05, 2022 1:13:50 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:13:49.621Z: Workers have started successfully.
Apr 05, 2022 1:14:06 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:14:03.913Z: 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
Apr 05, 2022 1:14:06 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:14:04.059Z: Executing operation 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step:
 0/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor)
Apr 05, 2022 1:14:27 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:14:24.348Z: Finished operation 
Read-input-ParDo-BoundedSourceAsSDFWrapper--ParMultiDo-BoundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing+ParDo(TimeMonitor)/ParMultiDo(TimeMonitor)+ParDo(ByteMonitor)/ParMultiDo(ByteMonitor)+Step:
 0/ParMultiDo(CounterOperation)+ParDo(TimeMonitor)2/ParMultiDo(TimeMonitor)
Apr 05, 2022 1:14:27 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:14:24.541Z: Cleaning up.
Apr 05, 2022 1:14:27 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:14:24.646Z: Stopping **** pool...
Apr 05, 2022 1:15:24 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:15:22.859Z: Autoscaling: Resized **** pool from 5 to 0.
Apr 05, 2022 1:15:24 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-04-05T13:15:22.914Z: Worker pool stopped.
Apr 05, 2022 1:15:29 PM org.apache.beam.runners.dataflow.DataflowPipelineJob 
logTerminalState
INFO: Job 2022-04-05_06_11_56-5811193247178506521 finished with status DONE.
Load test results for test (ID): c6bc3b74-6e89-4318-8709-48b54ca00977 and 
timestamp: 2022-04-05T13:11:50.877000000Z:
                 Metric:                    Value:
dataflow_v2_java17_runtime_sec                    15.382
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:20220405131117
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf
Tag: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220405131117]
- referencing digest: 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf]

Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220405131117] 
(referencing 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf])].
Removing untagged image 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf
Digests:
- 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf
Deleted 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:fd6362f49a9b6e2809a806f8d3c20ad781e268a0900096180556513b0c8e86bf].
Removing untagged image 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:9fdb0e3d5822e77bc90c30eea5af1286453a67ca0b5f45dac09bda7c8305157b
Digests:
- 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:9fdb0e3d5822e77bc90c30eea5af1286453a67ca0b5f45dac09bda7c8305157b
ERROR: (gcloud.container.images.delete) Not found: response: 
{'docker-distribution-api-version': 'registry/2.0', 'content-type': 
'application/json', 'date': 'Tue, 05 Apr 2022 13:15:39 GMT', 'server': 'Docker 
Registry', 'cache-control': 'private', 'x-xss-protection': '0', 
'x-frame-options': 'SAMEORIGIN', 'transfer-encoding': 'chunked', 'status': 
'404', 'content-length': '168', '-content-encoding': 'gzip'}
Failed to compute blob liveness for manifest: 
'sha256:9fdb0e3d5822e77bc90c30eea5af1286453a67ca0b5f45dac09bda7c8305157b': 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_ParDo_Dataflow_V2_Batch_Java17/ws/src/runners/google-cloud-dataflow-java/build.gradle'>
 line: 297

* 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.
> Run with --scan to get full insights.

* 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.3.2/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 4m 23s
105 actionable tasks: 8 executed, 97 up-to-date

Publishing build scan...
https://gradle.com/s/dmrzf5k7otihu

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