all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 63368@debbugs.gnu.org
Subject: bug#63368: Build coordiantor "Signals delivery fails constantly" crashes
Date: Wed, 10 May 2023 13:47:11 +0100	[thread overview]
Message-ID: <87jzxg1hd4.fsf@cbaines.net> (raw)
In-Reply-To: <87mt2fytxh.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]


Christopher Baines <mail@cbaines.net> writes:

> Since the recent core-updates merge, I've seen the build coordinator
> using less memory, but it's also been crashing in a new way, up to 10
> times a day.
>
> In the log, you see something like:
>
>   2023-05-07 09:15:42 Signals delivery fails constantly at GC #71051
>   2023-05-07 09:15:42 Signals delivery fails constantly
>
> I'm guessing the switch from libgc-8.0.4 to libgc-8.2.2 has something to
> do with this.

I think I've found a workaround. I found a list of environment variables
[1] you can set to affect the GC behaviour, and the first one I tried
(GC_RETRY_SIGNALS=0) seems to have had the desired affect, in that the
crashes/restarts have stopped.

1: https://github.com/ivmai/bdwgc/blob/master/docs/README.environment

I've sent a patch [2] to apply this setting as part of the service.

2: https://issues.guix.gnu.org/63417

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-05-10 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 10:45 bug#63368: Build coordiantor "Signals delivery fails constantly" crashes Christopher Baines
2023-05-10 12:47 ` Christopher Baines [this message]
2023-05-25 15:24 ` Ludovic Courtès
2023-05-25 15:26   ` Christopher Baines
2023-06-02 17:07     ` Christopher Baines
2023-06-06 15:09       ` Ludovic Courtès
2023-06-06 15:19         ` Christopher Baines
2023-06-09 13:14           ` Ludovic Courtès

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=87jzxg1hd4.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=63368@debbugs.gnu.org \
    /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.