From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#31925: 'guix substitutes' sometimes hangs on glibc 2.27
Date: Fri, 06 Jul 2018 17:35:22 +0200
Message-ID: <87fu0wbcn9.fsf@gnu.org>
References: <87bmc4748n.fsf@gnu.org> <874lhffpnq.fsf@gnu.org>
	<87tvpfaqfd.fsf@gnu.org> <87efgil5jz.fsf@netris.org>
	<87lgaqjemj.fsf@igalia.com> <87po01eul3.fsf@gnu.org>
	<87zhz5ixle.fsf@igalia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59300)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fbSmD-0006ui-Kv
	for bug-guix@gnu.org; Fri, 06 Jul 2018 11:36:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fbSmA-0007Ij-HJ
	for bug-guix@gnu.org; Fri, 06 Jul 2018 11:36:05 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:40886)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1fbSmA-0007IZ-DO
	for bug-guix@gnu.org; Fri, 06 Jul 2018 11:36:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.31925.B31925.15308913368131@debbugs.gnu.org>
In-Reply-To: <87zhz5ixle.fsf@igalia.com> (Andy Wingo's message of "Thu, 05 Jul
	2018 16:08:45 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Andy Wingo <wingo@igalia.com>
Cc: 31925@debbugs.gnu.org

Hello Andy,

Andy Wingo <wingo@igalia.com> skribis:

> On Thu 05 Jul 2018 14:27, ludo@gnu.org (Ludovic Court=C3=A8s) writes:
>
>> Hello,
>>
>> Andy Wingo <wingo@igalia.com> skribis:
>>
>>> The signal thread is a possibility though in that case you'd get a
>>> warning; the signal-handling thread appears in scm_all_threads.  Do you
>>> see a warning?  If you do, that is a problem :)
>>
>> I don=E2=80=99t see a warning.
>>
>> But as a Guile user, I shouldn=E2=80=99t see a warning just because ther=
e=E2=80=99s a
>> signal thread anyway; it=E2=80=99s not a thread I spawned myself.
>
> I understand but it's how it works.  If we want to change this, probably
> we need a similar interface as we have with finalization.

Right, understood.

>> scheme@(guile-user)> (all-threads)
>> $1 =3D (#<thread 140488743438080 (1b06c40)> #<thread 140488815434624 (1b=
06e00)>)
>> scheme@(guile-user)> (when (zero? (primitive-fork)) (primitive-_exit 0))
>> ;; no warning
>
> Are you certain that this is the signal-handling thread and not the
> finalizer thread?  I suspect it is the finalizer thread, and that it
> gets properly shut down before the fork.

Oh, you must be right.

> Regarding seeing the warning: do you do make some other binding for the
> default warning port in Guix?

No.

Thanks,
Ludo=E2=80=99.