From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Vong Subject: Re: guix-pull prints stack trace Date: Sat, 10 Sep 2016 20:22:32 +0800 Message-ID: <87oa3w7xmf.fsf@gmail.com> References: <877fakibfh.fsf@gmail.com> <87h99oqc1h.fsf@T420.taylan> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39560) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bihJ5-0005e6-6O for guix-devel@gnu.org; Sat, 10 Sep 2016 08:22:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bihJ1-0003r6-17 for guix-devel@gnu.org; Sat, 10 Sep 2016 08:22:50 -0400 Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]:36326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bihJ0-0003qF-QF for guix-devel@gnu.org; Sat, 10 Sep 2016 08:22:46 -0400 Received: by mail-pa0-x232.google.com with SMTP id id6so36806323pad.3 for ; Sat, 10 Sep 2016 05:22:46 -0700 (PDT) In-Reply-To: <87h99oqc1h.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Sat, 10 Sep 2016 12:33:46 +0200") 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: Taylan Ulrich =?utf-8?Q?=22Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer=22?= Cc: guix-devel@gnu.org taylanbayirli@gmail.com (Taylan Ulrich "Bay=C4=B1rl=C4=B1/Kammer") writes: > Alex Vong writes: > [...] > > The bug I introduced to guix pull (while speeding it up) that has a tiny > chance of causing a thread race related error has never been fixed. > Maybe it's related to that. > > As of e714797 I can't reproduce the error; guix pull runs fine to > completion. Possibly a commit after c41d97b "fixed" the issue again by > changing the order of autoloads or some such. But it could also be > related to the number of cores on my machine, how much you moved around > your pointer device recently, or the phase of the moon. :-\ > > If you still hit the error, or anyone else does, I'll get to work on it > ASAP. > Yes, commit e714797 'gnu: pdf: Remove erroneous module import.' seems to have fixed the issue again. Thanks for your attention. I don't know there is a potential race condition in guix-pull. I will keep this in mind. > Otherwise, I'm quite out of the loop but IIRC there was some talk of an > entirely different guix pull mechanism, that uses git pull or so? If > so and if this bug continues to trigger extremely rarely, then I'm not > sure if it would be worth the effort to make bigger changes to the > current 'guix pull' mechanism. > > Taylan > > > P.S.: Feel free to contact me on Freenode (nick 'taylan') if you want to > bypass email for quicker communication. Thanks, Alex