public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com>,
	 Tobias Burnus <tobias@codesourcery.com>
Subject: Re: [PATCH (pushed)] sphinx: stop using parallel mode
Date: Fri, 11 Nov 2022 08:05:13 -0800	[thread overview]
Message-ID: <CA+=Sn1=1nKepgVacV=MmjPZGdLEKMy8o_p0COWy=6LFfU2uyPw@mail.gmail.com> (raw)
In-Reply-To: <161b50ae-626e-4e34-e3e8-d00cc4c29e14@suse.cz>

On Fri, Nov 11, 2022 at 4:34 AM Martin Liška <mliska@suse.cz> wrote:
>
> Noticed that the documentation build can stuck on a machine with
> many cores (160) and I identified a real sphinx problem:
> https://github.com/sphinx-doc/sphinx/issues/10969
>
> Note the parallel can help just for some manuals and it is not critical
> for us.

This alone should cause us to pause and just revert back to texinfo.
People are not going to upgrade sphinx all the time just to get fixes
for documentation layout.
Texinfo is stable and we should just revert back to it.

Thanks,
Andrew Pinski

>
> ChangeLog:
>
>         * doc/Makefile: Disable -j auto.
> ---
>  doc/Makefile | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/doc/Makefile b/doc/Makefile
> index 9e305a8e7da..e08a43ecf2d 100644
> --- a/doc/Makefile
> +++ b/doc/Makefile
> @@ -2,7 +2,11 @@
>  #
>
>  # You can set these variables from the command line.
> -SPHINXOPTS   ?= -j auto -q
> +
> +# Disable parallel reading as it can be very slow on a machine with CPUs:
> +# https://github.com/sphinx-doc/sphinx/issues/10969
> +
> +SPHINXOPTS   ?= -q
>  SPHINXBUILD  ?= sphinx-build
>  PAPER        ?=
>  SOURCEDIR     = .
> --
> 2.38.1
>

      reply	other threads:[~2022-11-11 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 12:33 Martin Liška
2022-11-11 16:05 ` Andrew Pinski [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

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

  git send-email \
    --in-reply-to='CA+=Sn1=1nKepgVacV=MmjPZGdLEKMy8o_p0COWy=6LFfU2uyPw@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=tobias@codesourcery.com \
    /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 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).