@samitouri / QOSamiQemu / commits / c3662589c4

docs: fix sphinx build failure

We recently started to have those failures appearing when building documentation. It's hard to identify if it comes from a python, sphinx or sphinx extension, but it blocks us. Exception occurred: File "/usr/lib/python3.13/multiprocessing/connection.py", line 399, in _recv raise EOFError EOFError The full traceback has been saved in /tmp/sphinx-*.log, if you want to report the issue to the developers. This seems to be the generic error message for "something went wrong in sphinx multiprocess": - https://github.com/sphinx-doc/sphinx/issues/11449 - https://github.com/sphinx-doc/sphinx/issues/14458 - https://github.com/sphinx-doc/sphinx/issues/8973 Solve the issue by simply going back to sequential builds. We didn't notice a huge speedup anyway. Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Link: https://lore.kernel.org/qemu-devel/20260720222717.33078-1-pierrick.bouvier@oss.qualcomm.com Signed-off-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>

Pierrick Bouvier committed Jul 20, 2026 at 22:27 UTC c3662589c4986fb7fcdda5ba6c71558e73ba759a

1 file changed +1 -1

docs/meson.build

+1 -1

@@ -4,7 +4,7 @@ sphinx_build = find_program(fs.parent(python.full_path()) / 'sphinx-build',

4 # Check if tools are available to build documentation.

5 build_docs = false

6 if sphinx_build.found()

7 - SPHINX_ARGS = ['env', 'CONFDIR=' + qemu_confdir, sphinx_build, '-q', '-j', 'auto']

7 + SPHINX_ARGS = ['env', 'CONFDIR=' + qemu_confdir, sphinx_build, '-q']

8 # If we're making warnings fatal, apply this to Sphinx runs as well

9 if get_option('werror')

10 SPHINX_ARGS += [ '-W', '-Dkerneldoc_werror=1' ]