From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: successful installation, but problems updating Date: Sat, 11 Nov 2017 20:26:39 -0500 Message-ID: <20171112012639.GB13886@jasmine.lan> References: <20171106210540.0271775c@jasniac.instanton> <87tvy6bg2y.fsf@gnu.org> <20171108023730.6756d899@jasniac.instanton> <877euzio7k.fsf@gnu.org> <20171109202737.19fd288b@jasniac.instanton> <20171109214624.2cc2d152@jasniac.instanton> <87efp7maw8.fsf@gmail.com> <20171110082612.502198ae@jasniac.instanton> <20171110163539.GB11031@jasmine.lan> <20171111232300.513d67fb@graviton.instanton> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eDh3N-0003TH-M0 for help-guix@gnu.org; Sat, 11 Nov 2017 20:27:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eDh3K-0005jf-GT for help-guix@gnu.org; Sat, 11 Nov 2017 20:27:17 -0500 Content-Disposition: inline In-Reply-To: <20171111232300.513d67fb@graviton.instanton> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Marco van Hulten Cc: help-guix@gnu.org --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2017 at 11:23:00PM +0100, Marco van Hulten wrote: > > This is terrible, but you can work around it by passing a large value to > > the --max-silent-time "common build option": [...] >=20 > Hmm, but the time-out is now after 1 hour of silence, and the whole > process takes over 10 hours before crashing. This option may be useful > if I set a very short time, though it remains to be seen if this ends > guix quickly. I will play around with it. You can also increase the timeout with the --timeout option. However, if it crashes no matter how long you let it run, that's a different problem. > Right now a `guix pull' results in a `dispatch-exception' in procedure > `struct_vtable: Wrong type argument in position 1 (expecting struct): > #'. It seems that GuixSD (or components) is strongly in > flux right now, so I will try again later and do a proper bug report if > problems persist. This is definitely not supposed to happen. Hopefully it's already been fixed but otherwise a bug report is welcome! > I'd like to test if it is swapping. I have 2 GiB of RAM in a 2-core > machine (Intel Core 2 Duo). I did notice that swap was not enabled yet > on my system, and that (during last `guix pull') around 95% of RAM was > used. >=20 > > > - it took over 10 h to give me back control, whereas this used to be > > > a bit over 2 h in previous tries; =20 > >=20 > > Do you mean that the computer becomes unresponsive? >=20 > Yes. I have a Core 2 Duo system with 3 GiB RAM and `guix pull` takes less than an hour and doesn't swap. > Is 2 GiB considered "memory-constrained"? I'd argue that it should not be, but due to the Guile bug it is. It may not be enough to run `guix pull` =E2=80=94 I don't know exactly how much me= mory is required. --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAloHo0wACgkQJkb6MLrK fwg7cxAA3JBqElgyB0Hw1x5aqBvuH4iKJEdmanj56T0t6+NQnXUn1003RdUF03WU ajKd4K8JERZW8aufw9eifF4u3UaVKhHO+Ioj4P/uqw2jwsy5AVvoVyehAldR2MUP YQ57Y6VZrNE9RTtVGIGTuPAqsuWNO+QyORwQyYbBSsAwFhcvWHoKH4S6KaOvT9GG 8sErTQcaqHOdpEdWXxwkuL0kdaWiarXKW6TM5+IEKj0p6i1Wk0sUXlbmRRddxQjA Q+u6aidqo6qq+gIZayrXRW/KyMG+g9i94ppPtZUp5a7MpyIUTFDwI+mKOT0mbXn/ Ij7+CXOUVBTjudVulPYnvKuE21d6VgTs1fOvOSrwdfckzuNa1a3r04J+jqaf/9y2 OF1c5udWbHbR16B1yRkhJv7GTQEpLn2fyujAJfbT7W3xIAOXnV4/K7PGn1vnx77w lr+UCo+gBcYtCAgLtvW28Gu5cEGOQeSbCtDh0QfLn78p7Zznk+XJNXZOykoHrD9U SXX/RNoyIPAokJuZoCscxbdEfoqw8eKy+cZsg6ko1rIFKEdp7gQB/Osp8DjbGd/D n8f9nfLJIVmzWtf+GWDpJQPlWEw2vrKd3nvOIwq8cfd6Y7lfOqonpX+HfYH7XXbM msh3w7QGHcNkzjvcHKKvSuR8q9GkiA+wmYfAkVbdxGmQJoMRSvk= =eJoz -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--