From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#40518: guix pull: Dependency guix-packages-base fails Date: Thu, 09 Apr 2020 17:30:48 +0200 Message-ID: <87zhbk1xsn.fsf@gnu.org> References: <3DTCFZZAVGJ4B.22Q96Q868VFQ8@wilsonb.com> <87lfn53skg.fsf@gnu.org> <1Z6E7NH7WBPL4.3SGTTMBBYVN5C@wilsonb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50647) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jMZ8x-0001Xp-LH for bug-guix@gnu.org; Thu, 09 Apr 2020 11:31:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jMZ8w-0003v4-GZ for bug-guix@gnu.org; Thu, 09 Apr 2020 11:31:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42801) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jMZ8w-0003un-D7 for bug-guix@gnu.org; Thu, 09 Apr 2020 11:31:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jMZ8w-00043L-An for bug-guix@gnu.org; Thu, 09 Apr 2020 11:31:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <1Z6E7NH7WBPL4.3SGTTMBBYVN5C@wilsonb.com> (elaexuotee@wilsonb.com's message of "Thu, 09 Apr 2020 20:22:22 +0900") 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-mx.org@gnu.org Sender: "bug-Guix" To: elaexuotee@wilsonb.com Cc: 40518@debbugs.gnu.org elaexuotee@wilsonb.com skribis: >> I=E2=80=99m pretty sure the issue is caused by =E2=80=98--debug=3D3=E2= =80=99. Could you try >> simply: >> >> guix build /gnu/store/waisnnl9nbmlbpfwbn50pif79fsdknf9-guix-packages-b= ase.drv > > Oh! I had no idea the --debug flag could affect build success. The origin= al issue I > encountered was with a plain `guix pull', but in an attempt to provide th= e most useful > diagnostics, I tried including --debug=3D3. In any event, it just so happ= ens that I > saved the output from the original pull command, which I am attaching in = case it > happens to prove helpful. Yeah, that =E2=80=98--debug=3D3=E2=80=99 leads to breakage is a bug. > As it turns out, I tried another pull just a bit earlier, which ended up = succeeding; > however, I went ahead and tried running the build you suggest like this: > > $ guix pull -S 1 # broken build happened with generation 1 > $ guix build --check /gnu/store/waisnnl9nbmlbpfwbn50pif79fsdknf9-guix= -packages-base.drv > The following derivation will be built: > /gnu/store/waisnnl9nbmlbpfwbn50pif79fsdknf9-guix-packages-base.drv > building /gnu/store/waisnnl9nbmlbpfwbn50pif79fsdknf9-guix-packages-ba= se.drv... > [321/554] compiling... 15.9% of 277 filesbuilder for `/gnu/store/wa= isnnl9nbmlbpfwbn50pif79fsdknf9-guix-packages-base.drv' failed due to signal= 9 (Killed) > build of /gnu/store/waisnnl9nbmlbpfwbn50pif79fsdknf9-guix-packages-ba= se.drv failed > View build log at '/var/log/guix/drvs/wa/isnnl9nbmlbpfwbn50pif79fsdkn= f9-guix-packages-base.drv.bz2'. > guix build: error: build of `/gnu/store/waisnnl9nbmlbpfwbn50pif79fsdk= nf9-guix-packages-base.drv' failed > > What could be causing the build to receive SIGKILL? It could be an out-of-memory (OOM) condition: this build phase is unfortunately very demanding currently (at least 2=C2=A0GiB or RAM I think). How much RAM do you have? (Of course it=E2=80=99s OK if you get substitutes for that and don=E2=80=99= t have to build it locally, which hopefully is often the case.) Thanks, Ludo=E2=80=99.