From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] gnu: nss: Update to 3.30.2 [fixes CVE-2017-5461].
Date: Sat, 22 Apr 2017 15:51:27 -0400 [thread overview]
Message-ID: <874lxg9q68.fsf@netris.org> (raw)
In-Reply-To: <878tmsevqa.fsf@fastmail.com> (Marius Bakke's message of "Sat, 22 Apr 2017 09:40:13 +0200")
Hi Marius,
Marius Bakke <mbakke@fastmail.com> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Unfortunately, even with "nss-increase-test-timeout.patch" and
>> "nss-disable-long-b64-tests.patch", the build still failed on armhf:
>>
>> https://hydra.gnu.org/build/2010324
>
> This looks very similar to the random connect timeouts that prompted the
> "increase-test-timeouts" patch, except this time it took 50s instead of
> ~20s:
Thanks very much for looking into it.
50 seconds to make a local connection? Bah, that's ridiculous! I'm
beginning to wonder if the kernels running on these build slaves have
buggy schedulers resulting in starvation, or perhaps we're overloading
them too much.
> I am 99% sure the attached patch will do the job. What do you think?
If it sometimes takes 50 seconds to make a local connection, then I
suspect it could occasionally take much longer than a minute.
For now, I've asked Hydra to try building it again, as is.
Maybe in 'core-updates' we should consider increasing the timeout to
something on the order of 5 or 10 minutes.
What do you think?
Mark
next prev parent reply other threads:[~2017-04-22 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 22:29 [PATCHES] gnu: nss: Update to 3.30.2 [fixes CVE-2017-5461] Mark H Weaver
2017-04-21 17:59 ` Mark H Weaver
2017-04-22 7:40 ` Marius Bakke
2017-04-22 19:51 ` Mark H Weaver [this message]
2017-04-23 9:40 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lxg9q68.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.