From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCHES] gnu: nss: Update to 3.30.2 [fixes CVE-2017-5461]. Date: Sat, 22 Apr 2017 15:51:27 -0400 Message-ID: <874lxg9q68.fsf@netris.org> References: <87y3uun261.fsf@netris.org> <87lgqtzlon.fsf@netris.org> <878tmsevqa.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56821) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d214U-00068r-9W for guix-devel@gnu.org; Sat, 22 Apr 2017 15:51:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d214Q-0003PB-Cx for guix-devel@gnu.org; Sat, 22 Apr 2017 15:51:54 -0400 Received: from world.peace.net ([50.252.239.5]:53698) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d214Q-0003Fh-8Z for guix-devel@gnu.org; Sat, 22 Apr 2017 15:51:50 -0400 In-Reply-To: <878tmsevqa.fsf@fastmail.com> (Marius Bakke's message of "Sat, 22 Apr 2017 09:40:13 +0200") 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: Marius Bakke Cc: guix-devel@gnu.org 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 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