From: Christopher Baines <mail@cbaines.net>
To: 57596@debbugs.gnu.org
Subject: bug#57596: guix lint --checkers=derivation doesn't complete, Too many heap sections
Date: Tue, 06 Sep 2022 08:28:32 +0100 [thread overview]
Message-ID: <87v8q12c4t.fsf@cbaines.net> (raw)
In-Reply-To: <87zgfe2eta.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> When running the derivation checker on all packages for recent guix
> revisions, it dones't seem to complete. Instead, you get an error which
> I think comes from the garbage collection implementation that Guile
> uses:
>
> → guix lint --checkers=derivation
> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
> Aborted
>
> I noticed this on data.guix.gnu.org, as it effectively does something
> similar when trying to record the lint warnings for a revision.
>
> Maybe there's enough derivations now that the process of computing them
> all is too much for Guile? Or maybe it's something in the graph that's
> forming a loop?
I've got a bit more information now, I'm guessing the changes in [1]
just tipped the balance as that's when the data service instances
started not being able to process revisions.
1: https://git.savannah.gnu.org/cgit/guix.git/log/?qt=range&q=aae98c297214f87eb45302863adb021078c41a6f...d22a5c18517d662516fc93889534367fd3a448f2
I think I've managed to work around this now in the data service [2],
but the problem still remains when running the linter through the
script.
2: http://git.savannah.gnu.org/cgit/guix/data-service.git/commit/?id=b3d59c650a45429f90953e8fd865a3ba76a891cf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2022-09-06 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 12:14 bug#57596: guix lint --checkers=derivation doesn't complete, Too many heap sections Christopher Baines
2022-09-06 7:28 ` Christopher Baines [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
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=87v8q12c4t.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=57596@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 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).