-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Doc workflow is failing due to a missing file 'Doc/sphinx-warnings.txt' #118401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We upgraded Sphinx an hour ago: #118397 Thanks for the report, I'll check it. |
This is what's happening: The PR branch still has the old Sphinx 7.2: The error on the CI is actually in the previous step: sphinx-build: error: unrecognized arguments: --quiet --nitpicky --fail-on-warning --warning-file These long options were only added in Sphinx 7.3, and added to the workflow in #118397: make -C Doc/ PYTHON=../python SPHINXOPTS="--quiet --nitpicky --fail-on-warning --keep-going --warning-file sphinx-warnings.txt" html But your PR branch still has the short options: make -C Doc/ PYTHON=../python SPHINXOPTS="-q -n -W --keep-going -w sphinx-warnings.txt" html So it looks like, because the CI is started from a The quick solution is to update your branch from |
Please see PR #118403. |
(cherry picked from commit ee3413c) Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
Merged. I restarted this docs build and it failed again: It probably needs a new commit to re-sync or something? I updated the PR from Hopefully it won't happen again for new PRs. Thanks! |
Bug report
Bug description:
Example: https://github.com/python/cpython/actions/runs/8883326110/job/24389960128?pr=118368
The
'Doc/sphinx-warnings.txt'
file is a generated file so maybe we upgraded sphinx at some point and the new version does not generate the file if there's no warnings?CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: