unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: Kyle Meyer <kyle@kyleam.com>,  zimoun <zimon.toutoune@gmail.com>,
	 Arun Isaac <arunisaac@systemreboot.net>,
	 guix-devel@gnu.org
Subject: Re: Updating mumi on berlin
Date: Thu, 05 May 2022 10:45:07 -0400	[thread overview]
Message-ID: <87tua4jax8.fsf@gmail.com> (raw)
In-Reply-To: <877d70wtd7.fsf@kolabnow.com> (Thiago Jung Bauermann's message of "Thu, 05 May 2022 00:13:40 -0300")

Hi,

Thiago Jung Bauermann <bauermann@kolabnow.com> writes:

[...]

>> (IIRC, I think they're related to the lei tests expecting to be able
>> to kill the lei-daemon process, which isn't the case in Guix's build
>> environment.)
>
> Yes, that's what I'm seeing as well. The lei-daemon process is actually
> killed, but because of bug 30948 it is left in a zombie state and so the
> testsuite thinks that it didn't go away.

> The testsuite checks whether lei-daemon is gone by doing a
> “kill(<lei-daemon pid>, 0)”, which unfortunately succeeds for zombie processes.
>
> I've been meaning to add child reaping to the Guix builder process, but
> I'm moving very slowly due to time constraints and my unfamiliarity with
> that part of Guix...

Yes, that would be the correct and general solution (I hope you get to
fix it, else I may look into it in some time).  Workarounds currently in
use can be seen in our mutter package definition (it's a bit convoluted,
having to fork a process in which we set the child reaping property and
invoke the test suite via tini, acting as a fake PID 1).

HTH,

Maxim


  reply	other threads:[~2022-05-05 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22  5:38 Updating mumi on berlin Arun Isaac
2022-04-27  6:27 ` zimoun
2022-04-27 11:14   ` Arun Isaac
2022-05-02 10:33     ` zimoun
2022-05-03 17:33       ` Arun Isaac
2022-05-03 20:42       ` Thiago Jung Bauermann
2022-05-04  8:00         ` zimoun
2022-05-05  1:49           ` Kyle Meyer
2022-05-05  3:13             ` Thiago Jung Bauermann
2022-05-05 14:45               ` Maxim Cournoyer [this message]
2022-05-06  3:16                 ` Thiago Jung Bauermann
2022-05-07 22:20                 ` Ludovic Courtès
2022-05-08  1:00                   ` Thiago Jung Bauermann
2022-05-15 20:59                     ` Ludovic Courtès
2022-05-16  8:27                       ` Maxime Devos
2022-06-04 22:36                       ` Thiago Jung Bauermann
2022-05-05  8:37             ` zimoun
2022-05-06  2:24               ` public-inbox v1.7 update (was: Updating mumi on berlin) Kyle Meyer
2022-05-06  7:37                 ` zimoun
2022-05-08  4:41                   ` Kyle Meyer
2022-05-09 13:58                     ` zimoun
2022-05-06  3:22               ` Updating mumi on berlin Thiago Jung Bauermann
2022-05-06  7:48                 ` zimoun
2022-05-15 22:05                   ` Thiago Jung Bauermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tua4jax8.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=arunisaac@systemreboot.net \
    --cc=bauermann@kolabnow.com \
    --cc=guix-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).