From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 44491@debbugs.gnu.org
Subject: bug#44491: Support GUIX_DISABLE_NETWORK_TESTS environment variable
Date: Tue, 10 Nov 2020 22:26:49 +0100 [thread overview]
Message-ID: <87wnysnbs6.fsf@gnu.org> (raw)
In-Reply-To: <87k0utt6zt.fsf@yucca> (Vagrant Cascadian's message of "Tue, 10 Nov 2020 10:13:42 -0800")
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2020-11-08, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>
>>> If this could be considered for the upcoming 1.2 release, that would be
>>> appreciated, though I can also carry the patches in Debian...
>>
>> Yay! It should be doable, let’s see.
>
> It seems like a simpler workaround is to pass RES_OPTIONS=attempts:0,
> which should disable name resolution, and thus the network checks will
> fail.
>
> With the RES_OPTIONS workaround, the changes to guix/tests.scm
> network-reachable are no longer needed ... i think. :)
Oooh nice, the wonders of glibc!
> Might still be worth refactoring some of *.sh tests to use common
> functions, since the code is basically copied and pasted in several
> different places.
Yes, that’s still a good idea. Would you like to adjust your patch
accordingly?
> I suspect there are some additional tests that should check for network,
> but that is probably a separate bug once they have been identified.
OK!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-11-10 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 21:30 bug#44491: Support GUIX_DISABLE_NETWORK_TESTS environment variable Vagrant Cascadian
2020-11-08 17:46 ` Ludovic Courtès
2020-11-10 18:13 ` Vagrant Cascadian
2020-11-10 21:26 ` Ludovic Courtès [this message]
2020-11-11 3:39 ` Vagrant Cascadian
2020-11-11 6:06 ` Vagrant Cascadian
2020-12-03 17:09 ` Ludovic Courtès
2020-12-03 19:13 ` Vagrant Cascadian
2020-12-07 7:55 ` Ludovic Courtès
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=87wnysnbs6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44491@debbugs.gnu.org \
--cc=vagrant@debian.org \
/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).