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 #360
Date Tue, 12 Mar 2019 09:10:55 GMT
See <https://builds.apache.org/job/beam_Release_NightlySnapshot/360/display/redirect?page=changes>

Changes:

[coheigea] Use assertEquals(x, y) instead of assertTrue(x.equals(y))

[echauchot] [BEAM-6722] Raise embedded Cassandra startup timeout.

[heejong] [BEAM-6666] subprocess.Popen hangs after use of gRPC channel

[pabloem] Running Dataflow examples on windmill service

[thw] [BEAM-6796] [flink] Fully finish bundle before timer callback

[github] Update ReshuffleOverrideFactory to keep Reshuffle's

[25622840+adude3141] [BEAM-6726] explicitly specify signing key

[echauchot] [BEAM-6722] Add defensive code to avoid cleaning the cassandra cluster

[michal.walenia] [BEAM-6703] Added a Jenkins job to test a Direct runner compiled with

[chamikara] [BEAM-6748] Account for synchronization interval when estimating amount

[github] Update Python 3 support roadmap.

------------------------------------------
[...truncated 4.27 MB...]
`/` is not writable.
Bundler will use `/tmp/bundler/home/unknown' as your home directory temporarily.
Configuration file: /repo/website/_config.yml
Configuration file: /repo/website/_config_test.yml
            Source: /repo/website/src
       Destination: generated-local-content
 Incremental build: enabled
      Generating... 
                    done in 14.994 seconds.
 Auto-regeneration: disabled. Use --watch to enable.

> Task :beam-website:testWebsite
`/` is not writable.
Bundler will use `/tmp/bundler/home/unknown' as your home directory temporarily.
Running ["ImageCheck", "ScriptCheck", "LinkCheck", "HtmlCheck"] on ["./generated-local-content"]
on *.html... 



> Task :beam-vendor-sdks-java-extensions-protobuf:spotbugsMain

> Task :beam-website:testWebsite
Checking 891 external links...
Ran on 191 files!


- ./generated-local-content/beam/capability/2016/03/17/capability-matrix.html
  *  External link https://issues.apache.org/jira/browse/BEAM-19 failed: response code 0 means
something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed
out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: Server returned nothing
(no headers, no data)
  *  External link https://issues.apache.org/jira/browse/BEAM-9 failed: got a time out (response
code 0)
- ./generated-local-content/beam/release/2016/06/15/first-release.html
  *  External link https://issues.apache.org/jira/browse/BEAM/ failed: 429 No error
- ./generated-local-content/blog/2016/08/03/six-months.html
  *  External link https://issues.apache.org/jira/browse/BEAM-520?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(newbie%2C%20starter)
failed: 429 No error
- ./generated-local-content/blog/2017/01/09/added-apex-runner.html
  *  External link https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20and%20component%20%3D%20runner-apex%20and%20resolution%20%3D%20unresolved
failed: 429 No error
- ./generated-local-content/blog/2017/08/16/splittable-do-fn.html
  *  External link https://issues.apache.org/jira/browse/BEAM-2706 failed: got a time out
(response code 0)
- ./generated-local-content/contribute/docker-images/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM-4117 failed: response code 0
means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed
out.
             Sometimes, making 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/contribute/precommit-triage-guide/index.html
  *  External link https://issues.apache.org/jira/issues failed: 429 No error
- ./generated-local-content/contribute/release-guide/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
failed: 429 No error
  *  External link https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions
failed: 429 No error
- ./generated-local-content/documentation/io/built-in/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM-1678 failed: got a time out
(response code 0)
  *  External link https://issues.apache.org/jira/browse/BEAM-1857 failed: got a time out
(response code 0)
  *  External link https://issues.apache.org/jira/browse/BEAM-1893 failed: response code 0
means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed
out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: Server returned nothing
(no headers, no data)
  *  External link https://issues.apache.org/jira/browse/BEAM-2546 failed: got a time out
(response code 0)
  *  External link https://issues.apache.org/jira/browse/BEAM-3788 failed: response code 0
means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed
out.
             Sometimes, making 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-607 failed: got a time out (response
code 0)
  *  External link https://issues.apache.org/jira/browse/BEAM-67 failed: 429 No error
- ./generated-local-content/documentation/io/testing/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM-1025 failed: got a time out
(response code 0)
- ./generated-local-content/documentation/sdks/java/euphoria/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM-3900 failed: response code 0
means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed
out.
             Sometimes, making 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-1114 failed: got a time out
(response code 0)
  *  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: Server returned nothing
(no headers, no data)
  *  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: Server returned nothing
(no headers, no data)
  *  External link https://issues.apache.org/jira/browse/BEAM-2847 failed: got a time out
(response code 0)
  *  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 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
failed: 429 No error
- ./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-2285 failed: got a time out
(response code 0)
  *  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: got a time out (response
code 0)
- ./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: Server returned nothing
(no headers, no data)
  *  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
- ./generated-local-content/roadmap/java-sdk/index.html
  *  External link https://issues.apache.org/jira/browse/BEAM-2530 failed: got a time out
(response code 0)
- ./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
- ./generated-local-content/roadmap/python-sdk/index.html
  *  External link https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=245&view=detail
failed: 429 No error
rake aborted!
HTML-Proofer found 51 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:23: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
dd251d4e6472df548784548b67d6563c8693ac3885fea11b58eb46c3e3fd505d

> 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-io-kinesis:check
> Task :beam-sdks-java-io-kinesis:build
> Task :beam-vendor-sdks-java-extensions-protobuf:check
> Task :beam-vendor-sdks-java-extensions-protobuf:build
> Task :beam-sdks-java-test-utils:check
> Task :beam-sdks-java-test-utils:build
> Task :beam-sdks-java-load-tests:check
> Task :beam-sdks-java-load-tests: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 10m 7s
1059 actionable tasks: 917 executed, 142 from cache

Publishing build scan...
https://gradle.com/s/37dapyjlibxnq

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