Package: ruby-html-proofer
Version: 3.19.2-4
During rebuilds of debian-testing on our build systems (which have minimal
network available, in particular, they can only reach the local APT mirror,
we ran into the failure below.
IMHO, generally disabling checks via 'nocheck` in such an environment is
not a sensible option. Instead, packages should disable these tests or have
them conditional on previously successfully testing network access (i.e.
not just existence of a default route).
Failures:
1) Command test works with alt-ignore
Failure/Error: expect(output).to match('successfully')
expected "Running [\"ScriptCheck\", \"LinkCheck\", \"ImageCheck\"]
on spec/html-proofer/fixtures/images/ignora... message (if any) from the
server is: Couldn't resolve host name\n\nHTML-Proofer found 1 failure!\n"
to match "successfully"
Diff:
@@ -1,15 +1,29 @@
-successfully
+Running ["ScriptCheck", "LinkCheck", "ImageCheck"] on
spec/html-proofer/fixtures/images/ignorable_alt_via_options.html on
*.html...
+
+
+Checking 1 external link...
+Ran on 1 file!
+
+
+
+- spec/html-proofer/fixtures/images/ignorable_alt_via_options.html
+ * External link
http://upload.wikimedia.org/wikipedia/en/thumb/2/22/Heckert_GNU_white.svg/256px-Heckert_GNU_white.svg.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
+
+HTML-Proofer found 1 failure!
# ./spec/html-proofer/command_spec.rb:14:in `block (2 levels) in <top
(required)>'
