From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: Running individual system tests Date: Wed, 23 Oct 2019 15:04:13 +0200 Message-ID: <20191023150413.2c8ba41e@scratchpost.org> References: <7a1ea893-6ec0-5312-a013-cdc246a1e1e5@danielschaefer.me> <87wod0k59i.fsf@elephly.net> <20cc7df7-89bd-120b-d18d-c4a5b3bbbda3@danielschaefer.me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/=Si8x2kG_JcJ0DbbUS52ISm"; protocol="application/pgp-signature"; micalg=pgp-sha256 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41854) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNGJQ-0000Td-5n for guix-devel@gnu.org; Wed, 23 Oct 2019 09:04:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNGJL-00082l-3L for guix-devel@gnu.org; Wed, 23 Oct 2019 09:04:27 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:40118) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNGJK-0007zZ-SG for guix-devel@gnu.org; Wed, 23 Oct 2019 09:04:23 -0400 In-Reply-To: <20cc7df7-89bd-120b-d18d-c4a5b3bbbda3@danielschaefer.me> 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: Daniel =?ISO-8859-1?Q?Sch=E4fer?= Cc: guix-devel@gnu.org --Sig_/=Si8x2kG_JcJ0DbbUS52ISm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, On Wed, 23 Oct 2019 14:03:20 +0200 Daniel Sch=C3=A4fer wrote: > And I have to do it, whenever I want to run any system test, or build an= =20 > in-tree package (which I'm going to submit for inclusion)? Yes, in the end you have to do that. I agree that that's a very high bar of entry (for example compared to Gentoo ebuilds). But yes. > Or more precisely: It has to be run, once, before I do those things.=20 > Question: Doesn't it ever have to be rerun? How are new modules compiled? Yes. Ideally (in order to have a consistent state), delete the entire git clone of guix, then clone guix again and do it all over again. In practice I only invoke "make -j5" again. If that doesn't work, I invoke "./configure --localstatedir=3D/var" again and then "make -j5". This will incrementally compile new things so it will be quite fast. If the version of Guile got swapped before the second run of that stuff, the final result will be Frankenstein's monster, though, so I'm under no illusi= on that that's safe. > It takes 33 minutes on my laptop and is only going to take longer, when=20 > Guix gets bigger. -j5 > Is there maybe an interpreted mode? There is, but it is buggy. Ideally, nobody has to run "make" before any of this stuff (Guile can just interpret the scm files) but there's a strange bug where Guile then will use the wrong files (probably old compiled files from ~/.cache) if you do that, so I never do it anymore. --Sig_/=Si8x2kG_JcJ0DbbUS52ISm Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl2wT80ACgkQ5xo1VCww uqVaMwf+PzPyN0+8QuYA14zRpc+pZ0Ge7YgBg02AASMJfBznMPMIj1oW0S3DcxqM 5LnnwIjo5UEcnsL6/GxXgW6z25I1G9VC1g1n4py+Of0f84s2coLfR9DL+OeZ0XAZ 5zVF3qZP9gOclklzaoHTrbyTddxcFUfzvVUmdcpAdi1XAR5OofEwJ33hFBewz41Q cyCJHFw/F1y5ogBTUvsW5YAgtHKxf/WU3lDbHBzI4vTzR0uJvBjL+To/J9MlJXr1 cGJv2pNVHictYjTz4AIxWmsDQQrv+iwAChML/7m2YDB/WhIA4jQjDgDirsE4usNX 6sjZbRW+gZWElgzmRhnTDq3Br3f8mw== =qzBp -----END PGP SIGNATURE----- --Sig_/=Si8x2kG_JcJ0DbbUS52ISm--