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/03/05 12:10:44 UTC
Build failed in Jenkins: beam_PreCommit_Website_Cron #740
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/740/display/redirect?page=changes>
Changes:
[mxm] [BEAM-6731] Move ExpansionService to core-construction-java
------------------------------------------
[...truncated 54.95 KB...]
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/java/testing/nexmark/index.html
* External link https://issues.apache.org/jira/browse/BEAM-2112 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://issues.apache.org/jira/browse/BEAM-2176 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://issues.apache.org/jira/browse/BEAM-2847 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://issues.apache.org/jira/browse/BEAM-3961 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://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344540 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/mobile-gaming-example/index.html
* External link https://issues.apache.org/jira/browse/BEAM-4293 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://issues.apache.org/jira/browse/BEAM-4292 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://issues.apache.org/jira/browse/BEAM-791 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://issues.apache.org/jira/browse/BEAM-792 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
- ./generated-local-content/roadmap/connectors-python-sdk/index.html
* External link https://issues.apache.org/jira/browse/BEAM-4444 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/euphoria/index.html
* External link https://issues.apache.org/jira/browse/BEAM-4366?jql=project%20%3D%20BEAM%20AND%20component%20%3D%20dsl-euphoria 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/go-sdk/index.html
* External link https://issues.apache.org/jira/browse/BEAM-2083 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://issues.apache.org/jira/browse/BEAM-2939 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://issues.apache.org/jira/browse/BEAM-3301 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://issues.apache.org/jira/browse/BEAM-3304 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://issues.apache.org/jira/browse/BEAM-3306 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://issues.apache.org/jira/browse/BEAM-3612 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://issues.apache.org/jira/browse/BEAM-4115 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://issues.apache.org/jira/browse/BEAM-4124 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://issues.apache.org/jira/browse/BEAM-4152 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://issues.apache.org/jira/browse/BEAM-4726 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://issues.apache.org/jira/browse/BEAM-5379 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/java-sdk/index.html
* External link https://issues.apache.org/jira/browse/BEAM-2530 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/nemo-runner/index.html
* External link https://issues.apache.org/jira/projects/NEMO/issues/filter=allopenissues 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/portability/index.html
* External link https://issues.apache.org/jira/browse/BEAM-2862 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://issues.apache.org/jira/browse/BEAM-2863 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://issues.apache.org/jira/browse/BEAM-2896 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://issues.apache.org/jira/browse/BEAM-2899 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://issues.apache.org/jira/browse/BEAM-2925 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://issues.apache.org/jira/browse/BEAM-2937 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://issues.apache.org/jira/browse/BEAM-2940 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://issues.apache.org/jira/browse/BEAM-2941 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://issues.apache.org/jira/issues/?filter=12341256 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/python-sdk/index.html
* External link https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=245&view=detail 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 148 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
d1ab72199323925760cf8f3dba650f755a1ff28d8caeeb3ca79485eef3ba0e3e
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 13s
7 actionable tasks: 7 executed
Publishing build scan...
https://gradle.com/s/amcxoco4ztcmu
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 #741
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/741/display/redirect?page=changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org