See <https://builds.apache.org/job/beam_PreCommit_Website_Cron/163/display/redirect?page=changes>
Changes: [ankurgoenka] [BEAM-5284] Increase concurrency of java Portable VR tests [ankurgoenka] [BEAM-5697] Support legacy pipeline option deserialization [herohde] [BEAM-5698] Migration Go integration test to use Dataflow worker jar [mxm] [BEAM-5442] Store duplicate unknown options in a list argument [mxm] Update OWNERS file for runners-flink ------------------------------------------ [...truncated 167.04 KB...] * External link http://images/logos/runners/spark.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logos/sdks/go.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logos/sdks/java.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logos/sdks/python.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logos/sdks/scala.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/downloads/index.html * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/index.html * External link http://get-started/beam-overview failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://get-started/mobile-gaming-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 resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/mobile-gaming-example/index.html * External link http://documentation/programming-guide/ failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/programming-guide/ failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example-basic.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example-event-time-narrow.gif failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example-proc-time-narrow.gif failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example-session-windows.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example-team-scores-narrow.gif failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/gaming-example.gif failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/quickstart-go/index.html * External link http://documentation/sdks/go failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/quickstart-java/index.html * External link http://documentation/ failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/runners/apex failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/runners/dataflow failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/runners/flink failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/runners/spark failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/sdks/java failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/quickstart-py/index.html * External link http://documentation/resources failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://get-started/downloads failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://get-started/mobile-gaming-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 resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/get-started/wordcount-example/index.html * External link http://documentation/programming-guide failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://documentation/programming-guide failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/wordcount-pipeline.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/index.html * External link http://blog/2018/08/20/review-input-streaming-connectors.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 resolve host name * External link http://blog/2018/08/21/beam-summit-europe.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 resolve host name * External link http://blog/2018/10/03/beam-2.7.0.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 resolve host name * External link http://images/beam_architecture.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_apex.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_flink.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_gearpump.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_google_cloud.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_samza.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * External link http://images/logo_spark.png failed: response code 0 means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: Couldn't resolve host name * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> - ./generated-content/privacy_policy/index.html * http:// is an invalid URL (line 77) <a href="//" class="navbar-brand"> <img alt="Brand" style="height: 25px" src="//images/beam_logo_navbar.png"> </a> rake aborted! HTML-Proofer found 454 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 ':' Thread 2,5,main]) completed. Took 19.537 secs. :beam-website:stopAndRemoveDockerContainer (Thread[Task worker for ':' Thread 2,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 22abd6f9488d5b164f0ad493e34bba06291472dcf283b1520b0a486b2c643351 Successfully started process 'command 'docker'' 22abd6f9488d5b164f0ad493e34bba06291472dcf283b1520b0a486b2c643351 :beam-website:stopAndRemoveDockerContainer (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 4.568 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 Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/4.10.2/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 51s 8 actionable tasks: 8 executed Publishing build scan... https://gradle.com/s/qtqrnoh7t2dqk 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