TST: fail on warnings #647
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The configuration for failing on warnings is all OK, but the actual fix for the deprecation is a dead end currently as we run into a |
bsipocz
added
testing
|
For context and recent discussion about the deprecation and possible un-deprecation see sphinx-doc/sphinx#13083 |
bsipocz
force-pushed
the
TST_fail_on_warnings
branch
from
41db3f5
to
7311ff2
Compare
bsipocz
force-pushed
the
TST_fail_on_warnings
branch
2 times, most recently
from
d8309d1
to
4605fe1
Compare
bsipocz
force-pushed
the
TST_fail_on_warnings
branch
from
4605fe1
to
1b8a727
Compare
…gets triggered with the used version combo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix #645