Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Show errors and warnings in doc CI after build.#23868
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ae2f807
tof17bbbd
Compare9d17527
toeff2456
CompareIn addition, two examples are edited to not use "DeprecationWarning" and reflect the current status. |
eff2456
toc35de8c
Compare🎉 This is a very big win at a very small cost! |
Itshould be quite easy to get those results out and comment in the PR as well. Given that one knows how to do the GitHub-part... |
Great! 🚀 This addresses my issue#22176. Posting a commentis easyhttps://stackoverflow.com/a/64126737. |
@meeseeksdev backport to v3.6.2-doc |
@meeseeksdev backport to v3.6.x |
…868-on-v3.6.2-docBackport PR#23868 on branch v3.6.2-doc (Show errors and warnings in doc CI after build.)
…868-on-v3.6.xBackport PR#23868 on branch v3.6.x (Show errors and warnings in doc CI after build.)
Uh oh!
There was an error while loading.Please reload this page.
PR Summary
Adds a separate step that summarized the warnings and errors during documentation build.
Adds a step which checks for deprecation warnings in examples and tutorials.
I'm quite sure that there is an issue for that which I cannot find, but ideally this should be fed back to GitHub as a comment so it will still not be closed.
Anyway, this should help a bit as it is easier than scrolling back in the very long log (and some messages may have disappeared...).
Helps with#23866
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).