unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: guix QA "fails to process revision"
Date: Tue, 19 Sep 2023 18:12:16 +0100	[thread overview]
Message-ID: <878r92w0ar.fsf@cbaines.net> (raw)
In-Reply-To: <CAJsg1E-03pGp_MR38tdrATk8nhF0KfbBH46nHUSCmgyxo2wU3w@mail.gmail.com>

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


Andy Tai <atai@atai.org> writes:

> For a submitted patch, if Guix QA "fails to process revision" as in this log
> https://data.qa.guix.gnu.org/job/49399
>
> [ 32/ 40] compiling... 60.0% of 20 filesmadvise failed: Cannot allocate memory
> builder for `/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv'
> failed due to signal 11 (Segmentation fault)
> @ build-failed /gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv
> - 1 builder for
> `/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv' failed due
> to signal 11 (Segmentation fault)
> cannot build derivation
> `/gnu/store/yh45c2z642xv2m752i3mj4lahj7q4qxm-guix-cli.drv': 1
> dependencies couldn't be built
> ...
>
> what can be done about it?

I think in this case the machine (beid) was short on memory, it has 32GB
of RAM and 16GB of swap.

I've reduced the max processes for the data service processing new
revisions which should help, but there's probably more that can be done.

There looks to be regular spikes in the memory used by the data service
process, so it would be good to look in to why that happens, and what
can be done to avoid it.

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

  reply	other threads:[~2023-09-19 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 15:58 guix QA "fails to process revision" Andy Tai
2023-09-19 17:12 ` Christopher Baines [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-19 15:35 Andy Tai

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878r92w0ar.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=atai@atai.org \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).