From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Kyle Meyer <kyle@kyleam.com>,
Arun Isaac <arunisaac@systemreboot.net>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel@gnu.org
Subject: Re: Updating mumi on berlin
Date: Fri, 06 May 2022 00:22:36 -0300 [thread overview]
Message-ID: <87y1zftiba.fsf@kolabnow.com> (raw)
In-Reply-To: <86sfpo5q8w.fsf@gmail.com>
Hello,
zimoun <zimon.toutoune@gmail.com> writes:
> On Wed, 04 May 2022 at 21:49, Kyle Meyer <kyle@kyleam.com> wrote:
>
>> I've tried sit down and update Guix's public-inbox definition a few
>> times, but there are various test failures that I didn't figure out how
>> to handle in the time I had. (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.)
>
> On Thu, 05 May 2022 at 00:13, Thiago Jung Bauermann <bauermann@kolabnow.com> wrote:
>
>> 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...
>
> …why not just disable the specific test or if not possible, turn off the
> test suite ’#:tests? #f’. Whereas it is not the best, it would allow to
> have ’lei’ while waiting the fix at the Guix build environment level.
>
> WDYT?
I didn't go that route because I don't like disabling tests without
understanding why they fail and it took me a while to understand the
zombie root cause. In addition to that, without the testsuite passing I
didn't feel confident that I would be proposing a good enough package
because virtually the only part of public-inbox that I use is lei
itself. What if there was a regression in other parts of it and I didn't
notice because I use so little?
But I wouldn't mind disabling the part that checks that lei-daemon is
truly gone, or even the whole testsuite if that is too complicated.
On the other hand, the preferred solution would be the workaround
pointed out by Maxim, where tini is used to run the testsuite and reap
its sub-processes. I can probably take a stab at it over the weekend if
no one beats me to it.
>> $ guix shell -p path/to/profile -- lei up --all
>
> How do you query all new ones for a specific list?
>
>
> Thiago, do you use ’piem’ [1]?
I don't, but it looks interesting! I'll try it out, thanks!
> 1: <https://git.kyleam.com/piem/about/>
--
Thanks
Thiago
next prev parent reply other threads:[~2022-05-06 4:08 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
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 ` Thiago Jung Bauermann [this message]
2022-05-06 7:48 ` Updating mumi on berlin 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1zftiba.fsf@kolabnow.com \
--to=bauermann@kolabnow.com \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=maxim.cournoyer@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.