beam-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <jenk...@builds.apache.org>
Subject Build failed in Jenkins: beam_Release_NightlySnapshot #350
Date Sat, 02 Mar 2019 09:07:07 GMT
See <https://builds.apache.org/job/beam_Release_NightlySnapshot/350/display/redirect?page=changes>

Changes:

[ehudm] Allow setting dataflow_endpoint for Python ITs

[ttanay100] Fix link to Design Principles in PTransform Style Guide

[amaliujia] add missing bytes

[ttanay100] Change text as well

[github] Merge pull request #7353: [BEAM-4461] Support inner and outer style

[kenn] [BEAM-6554] Adjust Jenkins directory for spotbugs report

[kcweaver] [BEAM-6725] share some Flink job invocation code with Samza runner

[github] [BEAM-6711] Fix bq_to_table test for google (#7968)

------------------------------------------
[...truncated 4.21 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 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://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/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
  *  External link https://issues.apache.org/jira/browse/BEAM-2285 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-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-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-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 155 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
66a195b88d4dfb4798ab52c3ad269b1a956b290a642ea43b10c1127b8d261a3e

> 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
> Task :beam-sdks-java-test-utils:check
> Task :beam-sdks-java-test-utils:build
> Task :beam-vendor-sdks-java-extensions-protobuf:check
> Task :beam-vendor-sdks-java-extensions-protobuf:build
> Task :beam-sdks-java-io-xml:check
> Task :beam-sdks-java-io-xml: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 2h 6m 24s
1047 actionable tasks: 993 executed, 54 from cache

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

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


Mime
View raw message