See <https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Dataflow/5783/display/redirect>
Changes: ------------------------------------------ [...truncated 475.75 KB...] WARNING: 2020-05-08T12:01:38.865Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:39 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:37.952Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:39 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:39.090Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:42 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:41.551Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:44 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:43.715Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:46 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:44.334Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:47 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:46.527Z: Autoscaling: Raised the number of workers to 1 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:47 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:46.558Z: Resized worker pool to 1, though goal was 4. This could be a quota issue. May 08, 2020 12:01:48 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:47.379Z: Autoscaling: Raised the number of workers to 2 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:48 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:47.425Z: Resized worker pool to 2, though goal was 4. This could be a quota issue. May 08, 2020 12:01:48 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:48.118Z: Autoscaling: Raised the number of workers to 1 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:48 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:48.148Z: Resized worker pool to 1, though goal was 4. This could be a quota issue. May 08, 2020 12:01:49 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2020-05-08T12:01:46.759Z: Your project already contains 100 Dataflow-created metric descriptors and Stackdriver will not create new Dataflow custom metrics for this job. Each unique user-defined metric name (independent of the DoFn in which it is defined) produces a new metric descriptor. To 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 May 08, 2020 12:01:49 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:47.881Z: Autoscaling: Raised the number of workers to 2 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:49 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:47.917Z: Resized worker pool to 2, though goal was 4. This could be a quota issue. May 08, 2020 12:01:49 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:48.376Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:50 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:48.386Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:50 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:50.056Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:50 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:49.303Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:52 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:51.804Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:53 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:52.512Z: Autoscaling: Raised the number of workers to 2 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:53 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:52.548Z: Resized worker pool to 2, though goal was 4. This could be a quota issue. May 08, 2020 12:01:53 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:52.028Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:51.999Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:52.847Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:54.032Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:53.409Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:53.524Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:52.815Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:53.274Z: Autoscaling: Raised the number of workers to 3 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:56 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:53.319Z: Resized worker pool to 3, though goal was 4. This could be a quota issue. May 08, 2020 12:01:57 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:55.261Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:01:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:58.025Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:02:00 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:01:58.761Z: Autoscaling: Raised the number of workers to 4 based on the rate of progress in the currently running stage(s). May 08, 2020 12:02:05 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:05.645Z: Workers have started successfully. May 08, 2020 12:02:05 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:05.681Z: Workers have started successfully. May 08, 2020 12:02:07 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:06.686Z: Workers have started successfully. May 08, 2020 12:02:07 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:06.725Z: Workers have started successfully. May 08, 2020 12:02:08 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:07.077Z: Workers have started successfully. May 08, 2020 12:02:08 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:07.108Z: Workers have started successfully. May 08, 2020 12:02:10 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.667Z: Workers have started successfully. May 08, 2020 12:02:10 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.703Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.160Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.200Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.894Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:10.932Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.027Z: Workers have started successfully. May 08, 2020 12:02:11 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.074Z: Workers have started successfully. May 08, 2020 12:02:12 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.035Z: Workers have started successfully. May 08, 2020 12:02:12 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.073Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.441Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.480Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.013Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.051Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.656Z: Workers have started successfully. May 08, 2020 12:02:13 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:12.696Z: Workers have started successfully. May 08, 2020 12:02:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.845Z: Workers have started successfully. May 08, 2020 12:02:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:11.881Z: Workers have started successfully. May 08, 2020 12:02:15 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:13.662Z: Workers have started successfully. May 08, 2020 12:02:15 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:13.690Z: Workers have started successfully. May 08, 2020 12:02:17 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:15.860Z: Workers have started successfully. May 08, 2020 12:02:17 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:15.897Z: Workers have started successfully. May 08, 2020 12:02:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:16.526Z: Workers have started successfully. May 08, 2020 12:02:18 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2020-05-08T12:02:16.565Z: Workers have started successfully. May 08, 2020 12:02:28 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 2020-05-08_05_01_09-2253835307445704558 May 08, 2020 12:02:28 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 2020-05-08_05_01_16-7209152526581078605 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-12527710771384172255 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-13306521599109797675 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-13781631324822916661 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-2997847122946082165 May 08, 2020 12:02:28 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 2020-05-08_05_01_16-7574268915313725075 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-2327435852791993354 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-13803958173605836102 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-10644885366406910721 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-6933086923832199629 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-3107140163150648511 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-3045372037411656031 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-13019267892550531368 May 08, 2020 12:02:28 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 2020-05-08_05_01_09-6264679278774946730 > Task :sdks:java:testing:nexmark:run FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':sdks:java:testing:nexmark:run'. > Process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/java'' finished with > non-zero exit value 143 * 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 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.2.1/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 2m 10s 85 actionable tasks: 57 executed, 28 from cache Publishing build scan... The message received from the daemon indicates that the daemon has disappeared. Build request sent: Build{id=75851d65-d009-436e-a9ac-5abedc99bccd, currentDir=<https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Dataflow/ws/src}> Attempting to read last messages from the daemon log... Daemon pid: 19534 log file: /home/jenkins/.gradle/daemon/5.2.1/daemon-19534.out.log ----- Last 20 lines from daemon log file - daemon-19534.out.log ----- FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':sdks:java:testing:nexmark:run'. > Process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/java'' finished with > non-zero exit value 143 * 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 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.2.1/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 2m 10s 85 actionable tasks: 57 executed, 28 from cache Publishing build scan... Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. ----- 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 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]
