From 3c64c66238c06d26396a9c955eb58340e9e000c7 Mon Sep 17 00:00:00 2001 From: melanie witt Date: 2022年3月31日 04:39:15 +0000 Subject: [PATCH] Make 'tox -e fast-specs' fail on sphinx warnings I'm not sure if others will want this but when I made an edit on my spec and ran 'tox -e fast-specs', my expectation was that it was a fast way to check whether the edits I made would pass openstack-tox-docs in the gate. This turned out not to be the case, 'tox -e fast-specs' showed the "fast-specs: commands succeeded" message but when I uploaded the change, the openstack-tox-docs job failed because there was a sphinx parsing error in my spec. This adds -W to the sphinx-build call to treat warnings as errors to match 'tox -e docs' and openstack-tox-docs. It also runs sphinx-build via exec to make the script fail if sphinx-build returns non-zero. Change-Id: I9de750e7f44a746d4466c522004d0c2a624052e2 --- tools/fast-specs.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/fast-specs.sh b/tools/fast-specs.sh index 25596f272..d50d91a7a 100644 --- a/tools/fast-specs.sh +++ b/tools/fast-specs.sh @@ -50,7 +50,7 @@ for release in "${!specs_by_release[@]}"; do bld=doc/build/html/specs/$release files=${specs_by_release[$release]} echo "fast-specs: Building for ${release}:$files" - sphinx-build -c doc/source $src $bld $files + exec sphinx-build -W -c doc/source $src $bld $files # Save the full path to built files. (Wait until the end to output these, so # they're not lost between subdirectories.) for f in $files; do

AltStyle によって変換されたページ (->オリジナル) /