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 2019/02/25 08:57:13 UTC
Build failed in Jenkins: beam_Release_NightlySnapshot #345
See <https://builds.apache.org/job/beam_Release_NightlySnapshot/345/display/redirect?page=changes>
Changes:
[github] Update user-defined-function documentation
[sekikn] [BEAM-6432] Set dependent libraries' versions for the starter archetype
[kenn] [BEAM-6718] Fix BigQuery SQL postcommit (#7904)
------------------------------------------
[...truncated 4.16 MB...]
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/values/PCollection.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.transforms.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/resources/learning-resources/index.html
* External link https://beam.apache.org/get-started/quickstart-go/ failed: got a time out (response code 0)
- ./generated-local-content/documentation/runners/dataflow/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/runners/dataflow/options/DataflowPipelineOptions.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.options.pipeline_options.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/runners/direct/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/runners/direct/DirectOptions.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/io/Read.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/testing/PAssert.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/testing/TestStream.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/transforms/Create.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.options.pipeline_options.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.testing.util.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/runners/flink/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/runners/flink/FlinkPipelineOptions.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://flink.apache.org/downloads.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/runners/gearpump/index.html
* External link https://gearpump.apache.org/ failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/runners/samza/index.html
* External link http://samza.apache.org/ failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/documentation/runners/spark/index.html
* External link http://spark.apache.org/ failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/monitoring.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/monitoring.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/monitoring.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/monitoring.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/security.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/streaming-programming-guide.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/1.6.3/submitting-applications.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/latest/running-on-mesos.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/latest/running-on-yarn.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://spark.apache.org/docs/latest/spark-standalone.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/get-started/downloads/index.html
* External link http://www.apache.org/dyn/closer.cgi/beam/2.10.0/apache-beam-2.10.0-source-release.zip failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://www.apache.org/dyn/closer.cgi/beam/2.7.0/apache-beam-2.7.0-source-release.zip failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://www.apache.org/dyn/closer.cgi/beam/2.8.0/apache-beam-2.8.0-source-release.zip failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link http://www.apache.org/dyn/closer.cgi/beam/2.9.0/apache-beam-2.9.0-source-release.zip failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/javadoc/2.10.0/org/apache/beam/sdk/annotations/Experimental.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.10.0/apache-beam-2.10.0-source-release.zip.asc failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.10.0/apache-beam-2.10.0-source-release.zip.sha512 failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.7.0/apache-beam-2.7.0-source-release.zip.asc failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.7.0/apache-beam-2.7.0-source-release.zip.sha512 failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.8.0/apache-beam-2.8.0-source-release.zip.asc failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.8.0/apache-beam-2.8.0-source-release.zip.sha512 failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.9.0/apache-beam-2.9.0-source-release.zip.asc failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/2.9.0/apache-beam-2.9.0-source-release.zip.sha512 failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/dist/beam/KEYS failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://www.apache.org/info/verification.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/get-started/quickstart-py/index.html
* External link https://beam.apache.org/releases/pydoc failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/get-started/wordcount-example/index.html
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.io.gcp.pubsub.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.io.gcp.pubsub.html failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
- ./generated-local-content/roadmap/connectors-multi-sdk/index.html
* External link https://beam.apache.org/roadmap/portability/ failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Couldn't connect to server
rake aborted!
HTML-Proofer found 125 failures!
/usr/local/bundle/ruby/2.5.0/gems/html-proofer-3.9.3/lib/html-proofer/runner.rb:167:in `print_failed_tests'
/usr/local/bundle/ruby/2.5.0/gems/html-proofer-3.9.3/lib/html-proofer/runner.rb:48:in `run'
/repo/build/website/Rakefile:21:in `block in <top (required)>'
/usr/local/bundle/ruby/2.5.0/gems/rake-12.3.0/exe/rake:27:in `<top (required)>'
/usr/local/bundle/bin/bundle:23:in `load'
/usr/local/bundle/bin/bundle:23:in `<main>'
Tasks: TOP => test
(See full trace by running task with --trace)
> Task :beam-website:testWebsite FAILED
> Task :beam-website:stopAndRemoveDockerContainer
d8f104f6a3056845128638821920a0667426f1631650ce2cdcc072e1f4ba8e49
> Task :beam-website:buildWebsite
> Task :release:compileJava NO-SOURCE
> Task :release:compileGroovy FROM-CACHE
> Task :release:processResources NO-SOURCE
> Task :release:classes UP-TO-DATE
> Task :release:jar
> Task :release:assemble
> Task :release:compileTestJava NO-SOURCE
> Task :release:compileTestGroovy NO-SOURCE
> Task :release:processTestResources NO-SOURCE
> Task :release:testClasses UP-TO-DATE
> Task :release:test NO-SOURCE
> Task :release:check UP-TO-DATE
> Task :release:build
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':beam-website:testWebsite'.
> Process 'command 'docker'' 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 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 1h 56m 33s
1047 actionable tasks: 916 executed, 131 from cache
Publishing build scan...
https://gradle.com/s/qmd6jhpmctvuw
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
Build failed in Jenkins: beam_Release_NightlySnapshot #346
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_Release_NightlySnapshot/346/display/redirect?page=changes>
Changes:
[amaliujia] [sql][hotifx] remove less useful comments
[amaliujia] update
[github] [BEAM-6736] Upgrade gcsio dependency to 1.9.15
[robert] [BEAM-6738] Cache Combine Invokers.
[juta_staes] [BEAM-5627][BEAM-6569] run gcsio tests
[juta_staes] [BEAM-5315] add all tests to py3-gcp tox
[robert] Do not evict current working key.
------------------------------------------
[...truncated 5.26 MB...]
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-jdbc/2.12.0-SNAPSHOT/beam-sdks-java-io-jdbc-2.12.0-20190226.091047-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-jdbc/2.12.0-SNAPSHOT/beam-sdks-java-io-jdbc-2.12.0-20190226.091047-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
59: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-jms:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-jms/2.12.0-SNAPSHOT/beam-sdks-java-io-jms-2.12.0-20190226.091050-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-jms/2.12.0-SNAPSHOT/beam-sdks-java-io-jms-2.12.0-20190226.091050-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
60: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-kafka:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kafka/2.12.0-SNAPSHOT/beam-sdks-java-io-kafka-2.12.0-20190226.091056-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kafka/2.12.0-SNAPSHOT/beam-sdks-java-io-kafka-2.12.0-20190226.091056-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
61: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-kinesis:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kinesis/2.12.0-SNAPSHOT/beam-sdks-java-io-kinesis-2.12.0-20190226.091059-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kinesis/2.12.0-SNAPSHOT/beam-sdks-java-io-kinesis-2.12.0-20190226.091059-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
62: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-kudu:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kudu/2.12.0-SNAPSHOT/beam-sdks-java-io-kudu-2.12.0-20190226.091104-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-kudu/2.12.0-SNAPSHOT/beam-sdks-java-io-kudu-2.12.0-20190226.091104-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
63: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-mongodb:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-mongodb/2.12.0-SNAPSHOT/beam-sdks-java-io-mongodb-2.12.0-20190226.091108-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-mongodb/2.12.0-SNAPSHOT/beam-sdks-java-io-mongodb-2.12.0-20190226.091108-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
64: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-mqtt:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-mqtt/2.12.0-SNAPSHOT/beam-sdks-java-io-mqtt-2.12.0-20190226.091110-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-mqtt/2.12.0-SNAPSHOT/beam-sdks-java-io-mqtt-2.12.0-20190226.091110-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
65: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-parquet:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-parquet/2.12.0-SNAPSHOT/beam-sdks-java-io-parquet-2.12.0-20190226.091113-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-parquet/2.12.0-SNAPSHOT/beam-sdks-java-io-parquet-2.12.0-20190226.091113-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
66: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-rabbitmq:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-rabbitmq/2.12.0-SNAPSHOT/beam-sdks-java-io-rabbitmq-2.12.0-20190226.091119-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-rabbitmq/2.12.0-SNAPSHOT/beam-sdks-java-io-rabbitmq-2.12.0-20190226.091119-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
67: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-redis:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-redis/2.12.0-SNAPSHOT/beam-sdks-java-io-redis-2.12.0-20190226.091124-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-redis/2.12.0-SNAPSHOT/beam-sdks-java-io-redis-2.12.0-20190226.091124-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
68: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-solr:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-solr/2.12.0-SNAPSHOT/beam-sdks-java-io-solr-2.12.0-20190226.091129-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-solr/2.12.0-SNAPSHOT/beam-sdks-java-io-solr-2.12.0-20190226.091129-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
69: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-synthetic:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-synthetic/2.12.0-SNAPSHOT/beam-sdks-java-io-synthetic-2.12.0-20190226.091137-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-synthetic/2.12.0-SNAPSHOT/beam-sdks-java-io-synthetic-2.12.0-20190226.091137-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
70: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-tika:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-tika/2.12.0-SNAPSHOT/beam-sdks-java-io-tika-2.12.0-20190226.091142-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-tika/2.12.0-SNAPSHOT/beam-sdks-java-io-tika-2.12.0-20190226.091142-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
71: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-io-xml:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-xml/2.12.0-SNAPSHOT/beam-sdks-java-io-xml-2.12.0-20190226.091145-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-io-xml/2.12.0-SNAPSHOT/beam-sdks-java-io-xml-2.12.0-20190226.091145-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
72: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-load-tests:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-load-tests/2.12.0-SNAPSHOT/beam-sdks-java-load-tests-2.12.0-20190226.091153-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-load-tests/2.12.0-SNAPSHOT/beam-sdks-java-load-tests-2.12.0-20190226.091153-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
73: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-maven-archetypes-examples:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.12.0-SNAPSHOT/beam-sdks-java-maven-archetypes-examples-2.12.0-20190226.091200-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.12.0-SNAPSHOT/beam-sdks-java-maven-archetypes-examples-2.12.0-20190226.091200-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
74: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-maven-archetypes-starter:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-starter/2.12.0-SNAPSHOT/beam-sdks-java-maven-archetypes-starter-2.12.0-20190226.091202-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-starter/2.12.0-SNAPSHOT/beam-sdks-java-maven-archetypes-starter-2.12.0-20190226.091202-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
75: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-nexmark:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-nexmark/2.12.0-SNAPSHOT/beam-sdks-java-nexmark-2.12.0-20190226.091211-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-nexmark/2.12.0-SNAPSHOT/beam-sdks-java-nexmark-2.12.0-20190226.091211-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
76: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-sdks-java-test-utils:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-test-utils/2.12.0-SNAPSHOT/beam-sdks-java-test-utils-2.12.0-20190226.091214-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-test-utils/2.12.0-SNAPSHOT/beam-sdks-java-test-utils-2.12.0-20190226.091214-9.jar'. Received status code 401 from server: Unauthorized
* 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.
==============================================================================
77: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':beam-vendor-sdks-java-extensions-protobuf:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
> Could not write to resource 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.12.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.12.0-20190226.091218-9.jar'.
> Could not PUT 'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.12.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.12.0-20190226.091218-9.jar'. Received status code 401 from server: Unauthorized
* 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 14m 25s
945 actionable tasks: 748 executed, 197 up-to-date
Publishing build scan...
https://gradle.com/s/hhvvoh3wdvg5u
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