From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 33759@debbugs.gnu.org
Subject: [bug#33759] [PATCH] gnu: linkchecker: Fix build.
Date: Sun, 16 Dec 2018 16:12:23 +0100 [thread overview]
Message-ID: <87h8fdv73c.fsf@gnu.org> (raw)
In-Reply-To: <20181215121700.11320-1-mail@cbaines.net> (Christopher Baines's message of "Sat, 15 Dec 2018 12:17:00 +0000")
Hello Chris!
Christopher Baines <mail@cbaines.net> skribis:
> For some reason, the tests fail due to the lack of pytest. But when that's
> added as an input, then some tests fail in other ways.
>
> * gnu/packages/web.scm (linkchecker)[native-inputs]: Add python2-pytest.
> [arguments]: Set #:tests? to #f.
[...]
> + `(#:python ,python-2
> + ;; TODO: Tests currently fail. Looks to be a mixture of trying to use
> + ;; /homeless-shelter and maybe the network.
> + #:tests? #f))
Did you try adding a phase that does (setenv "HOME" (getcwd))?
IMO it would be best to get some confidence that the test failures are
benign, possibly working around them with tricks as above.
Thanks!
Ludo’.
next prev parent reply other threads:[~2018-12-16 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 12:17 [bug#33759] [PATCH] gnu: linkchecker: Fix build Christopher Baines
2018-12-16 15:12 ` Ludovic Courtès [this message]
2019-01-01 22:57 ` Christopher Baines
2019-01-03 21:34 ` [bug#33759] [PATCH v2 1/5] " Christopher Baines
2019-01-03 21:34 ` [bug#33759] [PATCH v2 2/5] gnu: Add python-miniboa Christopher Baines
2019-01-03 21:34 ` [bug#33759] [PATCH v2 3/5] gnu: python-2.7: Include /lib/python.../test/support Christopher Baines
2019-01-03 21:34 ` [bug#33759] [PATCH v2 4/5] gnu: python-futures: Enable tests Christopher Baines
2019-01-03 21:34 ` [bug#33759] [PATCH v2 5/5] gnu: linkchecker: Fix the package building Christopher Baines
2019-01-25 22:14 ` [bug#33759] [PATCH] gnu: linkchecker: Fix build Christopher Baines
2019-10-08 18:36 ` bug#33759: " Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8fdv73c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33759@debbugs.gnu.org \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).