See
<https://builds.apache.org/job/beam_PreCommit_Website_Cron/135/display/redirect?page=changes>
Changes:
[joar] [BEAM-5417] Parity between GCS and local match
[joar] Give test a more descriptive name
[joar] [BEAM-5417] ** matches anything, * matches [^/\]*
[joar] Make isort happy
[joar] Remove invalid sphinx references
[joar] Tidy up logging
[joar] Add test cases for {only,no}-root-level
[joar] Use str.join
[joar] Update FileSystems.match docstring
[joar] Remove reference to excluded method
[joar] Parameterize test_match_glob
[joar] Include CPython's license for translate_pattern
[thw] [BEAM-5625] Add missing CancelJobRequest parameter.
[joar] isort: Reorder imports
------------------------------------------
[...truncated 25.13 KB...]
Caching disabled for task ':beam-website:buildDockerImage': Caching has not
been enabled for the task
Task ':beam-website:buildDockerImage' 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 build -t beam-website .
Successfully started process 'command 'docker''
Sending build context to Docker daemon 26.03MB
Step 1/7 : FROM ruby:2.5
---> eb8759981348
Step 2/7 : WORKDIR /ruby
---> Using cache
---> 47bde9652e99
Step 3/7 : RUN gem install bundler
---> Using cache
---> 6a32cf966e7a
Step 4/7 : ADD Gemfile Gemfile.lock /ruby/
---> Using cache
---> ce0f03420ac0
Step 5/7 : RUN bundle install --deployment --path $GEM_HOME
---> Using cache
---> ee53f440d220
Step 6/7 : ENV LC_ALL C.UTF-8
---> Using cache
---> f536f6e61b6b
Step 7/7 : CMD sleep 3600
---> Using cache
---> 62a7ecf6b4b6
Successfully built 62a7ecf6b4b6
Successfully tagged beam-website:latest
:beam-website:buildDockerImage (Thread[Task worker for ':' Thread 11,5,main])
completed. Took 0.342 secs.
:beam-website:createDockerContainer (Thread[Task worker for ':' Thread
11,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 ':' Thread
11,5,main]) completed. Took 0.63 secs.
:beam-website:startDockerContainer (Thread[Task worker for ':' Thread
11,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
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b
Successfully started process 'command 'docker''
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b
:beam-website:startDockerContainer (Thread[Task worker for ':' Thread
11,5,main]) completed. Took 0.353 secs.
:beam-website:buildWebsite (Thread[Task worker for ':' Thread 11,5,main])
started.
> Task :rat
Build cache key for task ':rat' is 6ad44b750a061b9349628e69bbb1edf4
Caching disabled for task ':rat': Caching has not been enabled for the task
Task ':rat' is not up-to-date because:
No history is available.
Rat XML report:
<https://builds.apache.org/job/beam_PreCommit_Website_Cron/ws/src/build/reports/rat/rat-report.xml>
:rat (Thread[Task worker for ':',5,main]) completed. Took 3.42 secs.
> Task :beam-website:buildWebsite
Build cache key for task ':beam-website:buildWebsite' is
48a4c5e89a3173a1b3660896eaba2da8
Caching disabled for task ':beam-website:buildWebsite': Caching has not been
enabled for the task
Task ':beam-website:buildWebsite' 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
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b /bin/bash -c
cd /repo/build/website && bundle exec jekyll build --config
/repo/website/_config.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
Source: /repo/website/src
Destination: generated-content
Incremental build: enabled
Generating...
done in 18.216 seconds.
Auto-regeneration: disabled. Use --watch to enable.
:beam-website:buildWebsite (Thread[Task worker for ':' Thread 11,5,main])
completed. Took 20.011 secs.
:beam-website:testWebsite (Thread[Task worker for ':' Thread 11,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
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b /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 ["ScriptCheck", "ImageCheck", "HtmlCheck", "LinkCheck"] on
["./generated-content"] on *.html...
Checking 649 external links...
Ran on 157 files!
- ./generated-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)
- ./generated-content/beam/release/2016/06/15/first-release.html
* External link https://issues.apache.org/jira/browse/BEAM/ 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-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-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: Server
returned nothing (no headers, no data)
- ./generated-content/contribute/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-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: Server
returned nothing (no headers, no data)
* External link https://issues.apache.org/jira/browse/BEAM-3310 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-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)
* External link https://issues.apache.org/jira/browse/BEAM-4790 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-content/contribute/portability/index.html
* 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: Server
returned nothing (no headers, no data)
* 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: Server
returned nothing (no headers, no data)
* 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)
- ./generated-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: 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-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-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-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:
Failure when receiving data from the peer
- ./generated-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: Server
returned nothing (no headers, no data)
- ./generated-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)
rake aborted!
HTML-Proofer found 24 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:25: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 11,5,main])
completed. Took 30.561 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
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b
Successfully started process 'command 'docker''
0e5bef7d81547d6457c6dbc0691a401ea2444b0f97e8816276b7153a9b894d7b
:beam-website:stopAndRemoveDockerContainer (Thread[Task worker for ':',5,main])
completed. Took 0.617 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 1m 5s
8 actionable tasks: 8 executed
Publishing build scan...
https://gradle.com/s/txkohrwnvddac
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
