From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: Sphinx parallel build errors
Date: Wed, 9 Oct 2019 15:40:50 -0600 [thread overview]
Message-ID: <20191009154050.502061fa@lwn.net> (raw)
In-Reply-To: <dc19a670-7e8e-04e5-667d-578c2dd3754e@infradead.org>
On Wed, 9 Oct 2019 14:37:51 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> Sphinx parallel build error:
> OSError: [Errno 12] Cannot allocate memory
>
> I have had this error 4 times in the last 3 days.
>
> The first time it oom-killed Thunderbird. No big deal.
> The second time it oom-killed gimp, which had 24 photos open.
> Still no big deal. Just a nuisance.
>
> My little laptop has only 8 GB of RAM.
>
> Is there a way that I can limit the amount of parallelism?
Is this a change with current docs-next, or have you seen this for a
while? The parallelism logic changed a bit in docs-next, but the default
behavior should be the same as it was before.
"make -j 1 htmldocs" (in current docs-next) should give you a nice, slow,
serial build.
jon
next prev parent reply other threads:[~2019-10-09 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 21:37 Sphinx parallel build errors Randy Dunlap
2019-10-09 21:40 ` Jonathan Corbet [this message]
2019-10-09 22:18 ` Randy Dunlap
2019-10-10 2:30 ` Kees Cook
2019-10-10 3:00 ` Bhaskar Chowdhury
2019-10-10 18:48 ` Jonathan Corbet
2019-10-10 20:15 ` Randy Dunlap
2019-10-27 18:11 ` Randy Dunlap
2019-10-27 18:17 ` Jonathan Corbet
2019-10-27 18:30 ` Randy Dunlap
2019-10-27 19:05 ` Mauro Carvalho Chehab
2019-10-27 19:36 ` Randy Dunlap
2019-10-28 19:07 ` Kees Cook
2019-10-29 8:16 ` Markus Heiser
2019-10-29 16:09 ` Kees Cook
2019-10-29 19:41 ` Randy Dunlap
2019-10-29 19:57 ` Markus Heiser
2019-10-29 20:10 ` Randy Dunlap
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=20191009154050.502061fa@lwn.net \
--to=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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.
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.