Note: lists.yoctoproject.org will be down for maintenance on Wednesday, October 5th, starting at 9AM Pacific Time (4PM Wednesday October 5, 2022 UTC), for approximately one hour.
- [PATCH yocto-autobuilder-helper 4/4] Revert "scripts: run-docs-build: do not turn sphinx warnings into errors"
Re: [PATCH yocto-autobuilder-helper 4/4] Revert "scripts: run-docs-build: do not turn sphinx warnings into errors"
On Wed, 2022-06-22 at 14:50 +0200, Michael Opdenacker wrote:
On 3/15/22 17:31, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>We're trying to build the docs with Sphinx 5.0.0 on a special branch,
The patch was meant as a quick temporary work-around to have the docs
built and published.
Now that releases where -W flag is set (turning warnings into errors)
are appropriately patched to make those warnings disappear (on Sphinx
v3.2.1 which is the one used on the builder), this patch can be reverted
so that next time a warning appears the doc building will fail but will
not destroy the doc website (because of commit
6a4e6ef18d1415c719be51c773d7c57cae5549cf "scripts: run-docs-build: make
the script fail hard ASAP when there's an error", since rsync will not
be run if any error happens before).
This reverts commit 931d409b255a85f2217ca093d8391a678ce00ddb.
Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
scripts/run-docs-build | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 73cba3f..b9b331b 100755
@@ -33,14 +33,14 @@ cd $bbdocs
echo Building bitbake master branch
git checkout master
-SPHINXOPTS="-j auto" make publish
cp -r ./_build/final/* $outputdir/bitbake
and we're getting warnings causing the builds to fail:
If this patch hadn't been reverted, we would probably be fine.
What should we do now? Patch docs for all past Sphinx based releases? If
we tolerated warnings, we would have to do this less often when we want
to upgrade Sphinx.
In my opinion, another more trouble-free solution would be not to
regenerate docs for past releases, but instead only for the latest
commits in the branches we currently support.
What do you think?
We use the ability to regenerate previous releases to update the
switcher lists and potentially other style related changes in future
which keeps the docs looking consistent. We may have to disable the
errors on warnings :(
Join firstname.lastname@example.org to automatically receive all group messages.