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 18:13:16 UTC
Build failed in Jenkins: beam_PreCommit_Website_Cron #709
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/709/display/redirect?page=changes>
Changes:
[amaliujia] [sql][hotifx] remove less useful comments
[amaliujia] update
[github] [BEAM-6736] Upgrade gcsio dependency to 1.9.15
------------------------------------------
[...truncated 26.90 KB...]
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/dsls/sql/walkthrough/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/schemas/Schema.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/dsls/sql/windowing-and-triggering/index.html
* External link https://beam.apache.org/releases/pydoc/2.10.0/ 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/index.html
* External link http://flink.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/ 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/io/built-in/google-bigquery/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/org/apache/beam/sdk/extensions/gcp/options/GcpOptions.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.bigquery.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/io/developing-io-java/index.html
* External link https://beam.apache.org/releases/javadoc/current/index.html?org/apache/beam/sdk/io/gcp/datastore/DatastoreIO.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/io/developing-io-python/index.html
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.io.filebasedsink.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.iobase.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/programming-guide/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/Pipeline.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/documentation/sdks/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/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
- ./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/ 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/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://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
rake aborted!
HTML-Proofer found 92 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
e4191156f6f22b72214fc7dd6ba1fd70e5e796d53563703980158d9440cd663a
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
BUILD FAILED in 1m 17s
7 actionable tasks: 7 executed
Publishing build scan...
https://gradle.com/s/6jftjpme7lhze
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_PreCommit_Website_Cron #712
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/712/display/redirect?page=changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Build failed in Jenkins: beam_PreCommit_Website_Cron #711
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/711/display/redirect?page=changes>
Changes:
[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 44.79 KB...]
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/WithTimestamps.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/package-summary.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/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/wordcount-example/ 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/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/ 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/mapreduce/index.html
* External link https://hadoop.apache.org/docs/r1.2.1/single_node_setup.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/samza/index.html
* External link https://samza.apache.org/learn/documentation/latest/container/metrics-table.html failed: got a time out (response code 0)
* External link https://samza.apache.org/learn/documentation/latest/container/metrics.html failed: got a time out (response code 0)
- ./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/documentation/sdks/python-type-safety/index.html
* External link https://www.python.org/dev/peps/pep-0484/ failed: 503 No error
- ./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: got a time out (response code 0)
* 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-java/index.html
* External link https://beam.apache.org/releases/javadoc failed: got a time out (response code 0)
- ./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-go-sdk/index.html
* External link https://beam.apache.org/documentation/io/authoring-overview/ failed: got a time out (response code 0)
- ./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 140 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
a04cd21da48af42c7521cb9b91919961cac47fb95f900145b1bc8c9939f1727b
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
BUILD FAILED in 3m 39s
7 actionable tasks: 7 executed
Publishing build scan...
https://gradle.com/s/3kekhqqn5h5oi
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_PreCommit_Website_Cron #710
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/710/display/redirect>
------------------------------------------
[...truncated 32.57 KB...]
- ./generated-local-content/documentation/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
- ./generated-local-content/documentation/io/built-in/google-bigquery/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/org/apache/beam/sdk/extensions/gcp/options/GcpOptions.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/org/apache/beam/sdk/io/gcp/bigquery/BigQueryHelpers.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/io/developing-io-java/index.html
* External link https://beam.apache.org/releases/javadoc/current/index.html?org/apache/beam/sdk/io/gcp/datastore/DatastoreIO.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/io/developing-io-python/index.html
* External link https://beam.apache.org/releases/pydoc/2.10.0/apache_beam.io.filebasedsink.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.iobase.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/pipelines/test-your-pipeline/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/testing/package-summary.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/programming-guide/index.html
* External link https://beam.apache.org/releases/javadoc/2.10.0/index.html?org/apache/beam/sdk/Pipeline.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/Combine.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/Partition.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/WithTimestamps.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/package-summary.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/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
- ./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
- ./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
- ./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/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
rake aborted!
HTML-Proofer found 105 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
96b12773a5396a1a848471ea33ed2748ef58dc0972a45a3c3889f5fa0d349f52
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
BUILD FAILED in 2m 26s
7 actionable tasks: 7 executed
Publishing build scan...
https://gradle.com/s/y55pj5csnqufa
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