From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: [PATCHES] gnu: nss: Update to 3.30.2 [fixes CVE-2017-5461]. Date: Sun, 23 Apr 2017 11:40:07 +0200 Message-ID: <87r30j1myw.fsf@fastmail.com> References: <87y3uun261.fsf@netris.org> <87lgqtzlon.fsf@netris.org> <878tmsevqa.fsf@fastmail.com> <874lxg9q68.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2E06-00062h-Ef for guix-devel@gnu.org; Sun, 23 Apr 2017 05:40:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d2E03-0002bb-Bh for guix-devel@gnu.org; Sun, 23 Apr 2017 05:40:14 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:36007) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d2E03-0002Zh-3p for guix-devel@gnu.org; Sun, 23 Apr 2017 05:40:11 -0400 In-Reply-To: <874lxg9q68.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Mark H Weaver writes: > Hi Marius, > > Marius Bakke writes: >> Mark H Weaver 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've wondered about this too. Even x86_64 exceeded the default 5s timeout once. Maybe they are swapping to a busy I/O device? >> 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. This time a different test timed out at 34s. For now, I pushed the change for armhf only with timeout set to 5 minutes. Let's see how that goes. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlj8dncACgkQoqBt8qM6 VPpQBAgAn0R5g5inq1mS/kEq9FBoqsoZO2/V9r0KKm0FZz//JVE4PsqHJKtwQWR1 QmXW2t8zcIbwPN/EzWLgCf91cjkKxUZq2YtVhTLhnz9l2VQ3gsR17jxDI5PAOAs6 nzpFKsZyOtRVZ29Oz5FJwHyVP+KcU/NnQdx0d8P9lhOLAu3jOV50hKxi3QDKTdPk UF2O2UVwW2ssAcX1mcTlrcW9PeJexRdaWG8bg1gIkyG/+hj4DWMDJ5+OeT2VgjY/ AsI4P3RERGBFTdL0ekcGZh8Jz0bIrwpV7uZ2ugS6aI32wp6NI3eb3zDIenNezrD1 UiwSDh55te14zrd5ZCSg1Jbim8805Q== =GOq4 -----END PGP SIGNATURE----- --=-=-=--