From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Wingo Subject: Re: Preliminary IceCat 68.2 package Date: Wed, 23 Oct 2019 15:18:32 +0200 Message-ID: <87v9sfk3br.fsf@igalia.com> References: <87k18vzwl2.fsf@netris.org> <87blu7zr8f.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44230) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNGXW-0008JF-2j for guix-devel@gnu.org; Wed, 23 Oct 2019 09:19:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNGXU-0003AG-N8 for guix-devel@gnu.org; Wed, 23 Oct 2019 09:19:01 -0400 Received: from fanzine.igalia.com ([178.60.130.6]:35675) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNGXU-0002rd-0F for guix-devel@gnu.org; Wed, 23 Oct 2019 09:19:00 -0400 In-Reply-To: <87blu7zr8f.fsf@netris.org> (Mark H. Weaver's message of "Wed, 23 Oct 2019 06:32:37 -0400") 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: Mark H Weaver Cc: guix-devel@gnu.org Heya Mark :) On Wed 23 Oct 2019 12:32, Mark H Weaver writes: > I wrote: >> * Many earlier attempts to build it have failed due to non-deterministic >> failures in the build system, possibly due to a bug in the Cargo tool. >> I'm not sure how much luck was involved in my successful build. Your >> mileage may vary. > > Having now done a few more test builds, I'm sorry to say that the build > seems to often fail non-deterministically. Most of my attempts have > failed so far. > > The most common failure mode is described in these bug reports for > Gentoo and BLFS: > > https://bugs.gentoo.org/show_bug.cgi?id=680934 > http://wiki.linuxfromscratch.org/blfs/ticket/11975#comment:6 > > Those errors, where a backtrace is printed by cargo, happen at a > different place in the build every time. If you're lucky, you might get > through the entire build without hitting that bug. > > I'd be very grateful for help debugging these failures or finding a > workaround. I don't know what this is, but at work I have to build Firefox a lot, and sometimes the rust bits die in the middle of compilation. Is it a resource exhaustion issue? I am not sure. In any case, continuing to "make" always solves it for me. I know that's not very reassuring, but if you're looking for a quick workaround, running your "make -jN" in a loop 5 times or something may be good enough. Cheers, Andy