From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: 55954-done@debbugs.gnu.org
Subject: bug#55954: [PATCH] gnu: public-inbox: Fixes to allow the testsuite to run
Date: Fri, 17 Jun 2022 14:44:09 +0200 [thread overview]
Message-ID: <87v8szh33a.fsf@gnu.org> (raw)
In-Reply-To: <87bkushu4v.fsf@kolabnow.com> (Thiago Jung Bauermann's message of "Thu, 16 Jun 2022 23:38:50 -0300")
Hello,
Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> Applied, thanks!
>
> I guess you had second thoughts. :-)
Yes, sorry; I wasn’t sure whether bothering you was a good idea, but I
was also dissatisfied with that whole situation (which is not
public-inbox’s fault!).
>> It’s a bummer that we have to do all this. Would this work:
>>
>> (replace 'check
>> (lambda _
>> (sigaction SIGINT SIG_DFL)
>> (sigaction SIGTERM SIG_DFL)
>> (sigaction SIGCHLD (lambda _ (waitpid WAIT_ANY WNOHANG)))
>>
>> ;; Ugly hack to make sure signal handler asyncs get a chance
>> ;; to run while we’re in ‘waitpid’ during the “make check”
>> ;; invocation.
>> (sigaction SIGALRM (lambda _ (alarm 1)))
>> (alarm 1)))
>>
>> ?
>
> I assume there should be a "make check" in there somewhere. :-)
>
> Unfortunately, it didn't work. This is the check phase I tried:
>
> (replace 'check
> (lambda _
> (setenv "TEMP" "/tmp")
> (setenv "TEMPDIR" "/tmp")
> (setenv "TMP" "/tmp")
> (setenv "TMPDIR" "/tmp")
>
> (sigaction SIGINT SIG_DFL)
> (sigaction SIGTERM SIG_DFL)
> (sigaction SIGCHLD (lambda _ (waitpid WAIT_ANY WNOHANG)))
>
> ;; Ugly hack to make sure signal handler asyncs get a chance
> ;; to run while we’re in ‘waitpid’ during the “make check”
> ;; invocation.
> (sigaction SIGALRM (lambda _ (alarm 1)))
> (alarm 1)
> (unless (zero? (status:exit-val (system* "make" "check")))
> (error "`make check' exited with error"))))
>
>
> And this was the end of the output of the phase:
>
> ⋮
> Bailout called. Further testing stopped: daemon still running (PID:5282)
> FAILED--Further testing stopped: daemon still running (PID:5282)
> make: *** [Makefile:4141: check-each] Error 255
> error: in phase 'check': uncaught exception:
> misc-error #f "~A" ("`make check' exited with error") #f
> phase `check' failed after 27.7 seconds
>
> “daemon still running” means that lei's daemon process wasn't reaped.
Damnit, I wonder how that can happen.
>> If not, the solution you propose LGTM.
>
> Thanks. Hopefully this can be fixed in Guix's build machinery itself in
> the core-updates branch and all the packages that are using this hack
> can drop it then.
Yeah.
Anyway, applied for good this time, thanks for taking extra time on
this!
Ludo’.
prev parent reply other threads:[~2022-06-17 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 3:32 [bug#55954] [PATCH] gnu: public-inbox: Fixes to allow the testsuite to run Thiago Jung Bauermann via Guix-patches via
2022-06-16 9:27 ` Ludovic Courtès
2022-06-17 2:38 ` Thiago Jung Bauermann via Guix-patches via
2022-06-17 12:44 ` Ludovic Courtès [this message]
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=87v8szh33a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55954-done@debbugs.gnu.org \
--cc=bauermann@kolabnow.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.