From: "Ludovic Courtès" <ludo@gnu.org>
To: 37822@debbugs.gnu.org
Subject: bug#37822: guile-fibers build failure
Date: Tue, 22 Oct 2019 14:39:44 +0200 [thread overview]
Message-ID: <87v9sh2bu7.fsf@gnu.org> (raw)
In-Reply-To: <87k18zr37i.fsf@cbaines.net> (Christopher Baines's message of "Sun, 20 Oct 2019 13:50:09 +0100")
Hi Chris,
Christopher Baines <mail@cbaines.net> skribis:
> I've now tried running the tests using Guix immediately prior to the
> recent core-updates merge (d57660c54907cc6fba8b0adf6295fd2311ada6cf),
> and immediately after the merge
> (cf3d1763ede1a329c2bc932c84591ab594bb6c96) and the tests passed before,
> and failed afterwards.
>
> I've also tried running the tests manually, I did see a couple of times
> a failure that mentioned about "Too many open files" [1].
>
> I then attempted to raise the limit for open files, I think using
> prlimit like `prlimit --nofile=8096:8096 --pid GUIX_DAEMON_PID` did the
> trick, and that meant that I built the package sucessfully.
>
> I'm thinking now that there's a relationship between the number of cores
> the tests are run with, and the required file descriptors. Also, I'm
> pretty sure this behaviour changed when core-updates was merged.
Indeed, Fibers uses ‘epoll’ and for that it consumes file descriptors
proportionally to the number of threads, IIRC. You’d still have to have
a large number of threads to hit the default rlimit, but that’s not
impossible.
> I'll close this bug for now, as I've found a way to build the package.
To avoid “random” build failures, perhaps we should include a hack in
the ‘check’ phase, like calling ‘setrlimit’ right from there, WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-10-22 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 8:50 bug#37822: guile-fibers build failure Christopher Baines
2019-10-20 12:50 ` Christopher Baines
2019-10-22 12:39 ` Ludovic Courtès [this message]
2019-10-22 21:57 ` 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
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=87v9sh2bu7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37822@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).