Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Marius Bakke writes: > Marius Bakke writes: > >> Patch attached. I *think* the two values are for client and server >> respectively, but will study the source and build logs some more to make >> sure we're adjusting the right knobs. >> >> I suggest we

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Ludovic Courtès writes: > Marius Bakke skribis: > >> Marius Bakke writes: >> >>> Patch attached. I *think* the two values are for client and server >>> respectively, but will study the source and build logs some more to make >>> sure

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Marius Bakke skribis: > Marius Bakke writes: > >> Patch attached. I *think* the two values are for client and server >> respectively, but will study the source and build logs some more to make >> sure we're adjusting the right knobs. >> >> I suggest we

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Marius Bakke writes: > Patch attached. I *think* the two values are for client and server > respectively, but will study the source and build logs some more to make > sure we're adjusting the right knobs. > > I suggest we try this on 'core-updates' if the patch is correct.

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Leo Famulari writes: > On Tue, Mar 14, 2017 at 10:39:48PM +0100, Marius Bakke wrote: >> Going forward, I wonder if there could be any unintended side effects by >> simply increasing the timeouts in nss/gtests/ssl_gtest/tls_connect.cc >> from 5000 ms to something like 2.

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

On Tue, Mar 14, 2017 at 10:39:48PM +0100, Marius Bakke wrote: > Going forward, I wonder if there could be any unintended side effects by > simply increasing the timeouts in nss/gtests/ssl_gtest/tls_connect.cc > from 5000 ms to something like 2. If a 0-day is discovered in "nss", > we don't

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Leo Famulari writes: > On Tue, Mar 14, 2017 at 05:02:12PM -0400, Mark H Weaver wrote: >> This is not really sustainable. A single build attempt takes 7 hours on >> armhf, and about 40 hours on mips. When the failure occurs, it causes >> hundreds of other dependency

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

On Tue, Mar 14, 2017 at 05:02:12PM -0400, Mark H Weaver wrote: > This is not really sustainable. A single build attempt takes 7 hours on > armhf, and about 40 hours on mips. When the failure occurs, it causes > hundreds of other dependency failures, which must be restarted manually, > one at a

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Marius Bakke writes: > I have built this without trouble on two different x86_64 systems. The > release notes[0] lists a single entry[1] which looks innocuous[2], so I > doubt the failure is related to the upgrade. > > I can't find the build log of the first run, When

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Mark H Weaver writes: > Hi Marius, > > mba...@fastmail.com (Marius Bakke) writes: >> mbakke pushed a commit to branch master >> in repository guix. >> >> commit 4f3dcdd99ba13ab3bdbf1e014afcd076cd95fac7 >> Author: Marius Bakke >> Date: Mon Mar 13 16:53:27

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

I wrote: > If this problem cannot be fixed very soon, we'll need to revert this > update. One more thing: If you decide to revert the nss update (commit 4f3dcdd99b), please also revert commit 87f1c7efc1 (gnu: nss: Use 'modify-phases' syntax), to save Hydra from needlessly rebuilding several

Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.

Hi Marius, mba...@fastmail.com (Marius Bakke) writes: > mbakke pushed a commit to branch master > in repository guix. > > commit 4f3dcdd99ba13ab3bdbf1e014afcd076cd95fac7 > Author: Marius Bakke > Date: Mon Mar 13 16:53:27 2017 +0100 > > gnu: nss, nss-certs: Update to