From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 63417@debbugs.gnu.org
Subject: [bug#63417] [PATCH] services: guix-build-coordinator: Set GC_RETRY_SIGNALS=0.
Date: Fri, 01 Sep 2023 10:21:56 -0400 [thread overview]
Message-ID: <87r0ni2cu3.fsf@gmail.com> (raw)
In-Reply-To: <77bc127265325bc2c593abee09d08b79dc578566.1683722725.git.mail@cbaines.net> (Christopher Baines's message of "Wed, 10 May 2023 13:45:25 +0100")
Hi Christopher,
Christopher Baines <mail@cbaines.net> writes:
> This seems to work around the crashes/restarts that have recently been
> affecting the coordinator (see #63368).
>
> * gnu/services/guix.scm (guix-build-coordinator-shepherd-services): Set
> GC_RETRY_SIGNALS=0.
> ---
> gnu/services/guix.scm | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/gnu/services/guix.scm b/gnu/services/guix.scm
> index 90310ab9d9..f8fee38b7a 100644
> --- a/gnu/services/guix.scm
> +++ b/gnu/services/guix.scm
> @@ -372,6 +372,11 @@ (define (guix-build-coordinator-shepherd-services config)
> "GUIX_LOCPATH=" #$glibc-utf8-locales "/lib/locale")
> "LC_ALL=en_US.utf8"
> "PATH=/run/current-system/profile/bin" ; for hooks
> + ;; TODO: This seems to help with avoid
> + ;; crashes/restarts, but ideally the Guix service
> + ;; wouldn't be setting environment variables to fiddle
> + ;; with the behaviour of Guile's GC.
> + "GC_RETRY_SIGNALS=0"
> #$@extra-environment-variables)
> #:log-file "/var/log/guix-build-coordinator/coordinator.log")
> args))))
Have you tried presenting the problem to more core Guile folks?
(guile-devel). Perhaps someone could tip you in the right direction, or
perhaps it's a bug in Guile?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-09-01 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 12:45 [bug#63417] [PATCH] services: guix-build-coordinator: Set GC_RETRY_SIGNALS=0 Christopher Baines
2023-09-01 14:21 ` Maxim Cournoyer [this message]
2023-09-05 11:20 ` bug#63417: " Christopher Baines
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=87r0ni2cu3.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=63417@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.