See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/362/display/redirect?page=changes>
Changes: [ccy] Revert "Merge pull request #7051 from ------------------------------------------ [...truncated 28.28 KB...] Step 7/7 : CMD sleep 3600 ---> Running in b3cb367f7507 ---> e70f43e86b30 Removing intermediate container b3cb367f7507 Successfully built e70f43e86b30 Successfully tagged beam-website:latest :beam-website:buildDockerImage (Thread[Task worker for ':',5,main]) completed. Took 1 mins 23.575 secs. :beam-website:createDockerContainer (Thread[Task worker for ':',5,main]) started. > Task :beam-website:createDockerContainer Caching disabled for task ':beam-website:createDockerContainer': Caching has not been enabled for the task Task ':beam-website:createDockerContainer' is not up-to-date because: Task has not declared any outputs despite executing actions. Starting process 'command '/bin/bash''. Working directory: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/website> Command: /bin/bash -c docker create -v <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src>:/repo -u $(id -u):$(id -g) beam-website Successfully started process 'command '/bin/bash'' :beam-website:createDockerContainer (Thread[Task worker for ':',5,main]) completed. Took 0.134 secs. :beam-website:startDockerContainer (Thread[Task worker for ':',5,main]) started. > Task :beam-website:startDockerContainer Caching disabled for task ':beam-website:startDockerContainer': Caching has not been enabled for the task Task ':beam-website:startDockerContainer' is not up-to-date because: Task has not declared any outputs despite executing actions. Starting process 'command 'docker''. Working directory: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/website> Command: docker start 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c Successfully started process 'command 'docker'' 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c :beam-website:startDockerContainer (Thread[Task worker for ':',5,main]) completed. Took 0.282 secs. :beam-website:buildLocalWebsite (Thread[Task worker for ':',5,main]) started. > Task :beam-website:buildLocalWebsite Build cache key for task ':beam-website:buildLocalWebsite' is c21b294a46471ed295d0448d2143814d Caching disabled for task ':beam-website:buildLocalWebsite': Caching has not been enabled for the task Task ':beam-website:buildLocalWebsite' is not up-to-date because: No history is available. Starting process 'command 'docker''. Working directory: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/website> Command: docker exec 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c /bin/bash -c cd /repo/build/website && bundle exec jekyll build --destination generated-local-content --config /repo/website/_config.yml,/repo/website/_config_test.yml --incremental --source /repo/website/src Successfully started process 'command 'docker'' `/` 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 12.192 seconds. Auto-regeneration: disabled. Use --watch to enable. :beam-website:buildLocalWebsite (Thread[Task worker for ':',5,main]) completed. Took 13.801 secs. :beam-website:testWebsite (Thread[Task worker for ':',5,main]) started. > Task :beam-website:testWebsite Caching disabled for task ':beam-website:testWebsite': Caching has not been enabled for the task Task ':beam-website:testWebsite' is not up-to-date because: Task has not declared any outputs despite executing actions. Starting process 'command 'docker''. Working directory: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/website> Command: docker exec 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c /bin/bash -c cd /repo/build/website && bundle exec rake test Successfully started process 'command 'docker'' `/` is not writable. Bundler will use `/tmp/bundler/home/unknown' as your home directory temporarily. Running ["HtmlCheck", "ImageCheck", "ScriptCheck", "LinkCheck"] on ["./generated-local-content"] on *.html... Checking 724 external links... Ran on 178 files! - ./generated-local-content/beam/capability/2016/03/17/capability-matrix.html * External link https://issues.apache.org/jira/browse/BEAM-79 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./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: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./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: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Failure when receiving data from the peer - ./generated-local-content/blog/2018/10/29/beam-2.8.0.html * External link https://issues.apache.org/jira/browse/BEAM-4783 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./generated-local-content/contribute/index.html * External link https://issues.apache.org/jira/projects/BEAM/issues failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Failure when receiving data from the peer - ./generated-local-content/contribute/release-guide/index.html * External link https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Failure when receiving data from the peer - ./generated-local-content/documentation/io/authoring-overview/index.html * External link https://issues.apache.org/jira/browse/BEAM-65 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./generated-local-content/documentation/io/built-in/index.html * External link https://issues.apache.org/jira/browse/BEAM-3099 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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-4828 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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-607 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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-67 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./generated-local-content/documentation/runners/capability-matrix/index.html * External link https://issues.apache.org/jira/browse/BEAM-91 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the 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) - ./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: Server returned nothing (no headers, no data) - ./generated-local-content/get-started/downloads/index.html * External link https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343654 failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Failure when receiving data from the peer - ./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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) - ./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: Server returned nothing (no headers, no data) - ./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: Server returned nothing (no headers, no data) - ./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-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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) - ./generated-local-content/roadmap/portability/index.html * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) * 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: Server returned nothing (no headers, no data) - ./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: Failure when receiving data from the peer rake aborted! HTML-Proofer found 31 failures! /usr/local/bundle/ruby/2.5.0/gems/html-proofer-3.8.0/lib/html-proofer/runner.rb:167:in `print_failed_tests' /usr/local/bundle/ruby/2.5.0/gems/html-proofer-3.8.0/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 :beam-website:testWebsite (Thread[Task worker for ':',5,main]) completed. Took 45.689 secs. :beam-website:stopAndRemoveDockerContainer (Thread[Task worker for ':',5,main]) started. > Task :beam-website:stopAndRemoveDockerContainer Caching disabled for task ':beam-website:stopAndRemoveDockerContainer': Caching has not been enabled for the task Task ':beam-website:stopAndRemoveDockerContainer' is not up-to-date because: Task has not declared any outputs despite executing actions. Starting process 'command 'docker''. Working directory: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/website> Command: docker rm -f 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c Successfully started process 'command 'docker'' 939f38b865f9f6465f65ad8e74da7213c31e230362bd6420d57e39ef8612fc1c :beam-website:stopAndRemoveDockerContainer (Thread[Task worker for ':',5,main]) completed. Took 0.397 secs. 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 --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 32s 7 actionable tasks: 7 executed Publishing build scan... https://gradle.com/s/zc7rd3xwm74pq Closing Git repo: <https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/.git> Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
