Christopher Baines writes: > Ludovic Courtès writes: > >> Christopher Baines skribis: >> >>> 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. >> >> Normally on GNU/Linux libgc has: >> >> #define SIG_SUSPEND SIGPWR >> >> The Coordinator fiddles with SIGALRM, SIGUSR1, SIGINT, and SIGPIPE, >> which should normally be fine. >> >> Is there anything else that might interfere with libgc? > > I've seen this issue in both the build coordinator and nar-herder, both > of which use guile-sqlite, so I wonder if that could have something to > do with it. I've seen this happen with the build coordinator agent now (on milano-guix-1): 2023-06-02 18:59:55 2023-06-02 18:59:55 (DEBUG): fb9f06cf-cc1d-4493-88b8-3eac9437f5d4: checking the availability of build inputs 2023-06-02 18:59:55 2023-06-02 18:59:55 (INFO ): fb9f06cf-cc1d-4493-88b8-3eac9437f5d4: setup successful, building: /gnu/store/7fbrli2a8nzn676q8gz2b0i0y0lr9nxv-r-quasr-1.40.0.drv 2023-06-02 19:00:46 Signals delivery fails constantly at GC #55 2023-06-02 19:01:22 Signals delivery fails constantly 2023-06-02 19:01:29 locale is en_US.utf8 2023-06-02 19:01:29 (gnutls version: 3.7.7, guix version: 1.4.0-6.dc5430c) Which is a bit more concerning, since the build coordinator agent is intentionally quite simple (no SQLite for example).