From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#34531: Guix profile fails on Overdrive 1000 Date: Mon, 18 Feb 2019 21:49:10 +0100 Message-ID: <87mumsom9l.fsf@fastmail.com> References: <20190218200552.GB1881@jurong> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:44408) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvprc-0002f0-9k for bug-guix@gnu.org; Mon, 18 Feb 2019 15:50:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvprX-0001CY-5F for bug-guix@gnu.org; Mon, 18 Feb 2019 15:50:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:53972) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gvprW-0001BA-F5 for bug-guix@gnu.org; Mon, 18 Feb 2019 15:50:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gvprW-0006M7-8j for bug-guix@gnu.org; Mon, 18 Feb 2019 15:50:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190218200552.GB1881@jurong> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Andreas Enge , 34531@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Andreas Enge writes: > Hello, > > on a newly installed Overdrive 1000 machine with 8 GB of memory, I am try= ing > guix pull -n > > This results in > Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.= org/git/guix.git'... > Building from this channel: > guix https://git.savannah.gnu.org/git/guix.git d0d207c > The following derivations will be built: > /gnu/store/qvljgqnsynw113h1062nws9i2zfcz15y-compute-guix-derivation.drv > /gnu/store/rj824ibc8nhhl1j2h25sgw4lyxkxjggc-gdb-8.2.drv > ... > /gnu/store/w1jw283cdf6n03qnccsrvxgzy41z0hps-guile-gcrypt-0.1.0.drv > building /gnu/store/wy37294j2rb6fg5fgpybki28vq60jz94-python-minimal-3.6.5= .drv... > starting phase `set-SOURCE-DATE-EPOCH' > ... > > That a build of something starts although the "-n" flag is specified seems > to be a first bug. > > Then, during the test phase, the build is killed since the machine runs o= ut > of memory. I also tried to pass "--cores=3D1" to "guix build", but this > parameter is not honoured: "top" shows that all four cores are running. > This might be a second bug. > > In any case, it becomes impossible to upgrade with the usual mechanism, > which is a rather serious bug. > > My guix version: > $ guix --version > guix (GNU Guix) 0.15.0-8.71a78ba The Python contained within this Guix snapshot has a known bug that makes it leak memory on newer kernels. The Guix commit that works around it is 589aca1c183ef1dfdef54d40fdd6a258bbcd39d0. One thing you could try is bootstrap a Guix checkout through the usual mechanisms (./bootstrap; ./configure; etc), using packages from the host system if necessary. From=20there you should be able to "./pre-inst-env guix pull". A dirtier workaround is to delete "/tmp/guix-build-python-minimal-3.6.5.drv-0/Lib/test/test_socket.py" at some point during the build process, but you may have to do that a couple of times. Finally, installing 0.16.0 "from scratch" should also work. HTH! --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlxrGkYACgkQoqBt8qM6 VPpGXAgAyjE4PBegBmz7nZ9oqPkeRt7daBLQZzghxUcT6y3DiP9M9Qax4Tlc8dBo SzuOm7jvtPMjt7diLZfWLbj/IS8HoDwNKmiqUw4RZRovvVV6j6WKc5u6Q9UGdakX To9PoRgR6cmvOV+vb+cQm4xVPNouA6svw5PpZ3c+v67ii3iIxodtHb9jU6ACt9/j kwN4IWOvYAw+ua9dL/Tbl6Hl/eP0+cAOwwnWNDlPsGCDODCmQaq++T72+E+d3odW 1Q7py0vNl6zs3SLDVjsmAf0JCcAyjnuayubIWNn9BvpxwPVWgw+5Bd4s9kTBKX75 c2IirUdAnaY/32xCr1RSrmR7HJmQVw== =faAR -----END PGP SIGNATURE----- --=-=-=--