-
Notifications
You must be signed in to change notification settings - Fork 326
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
tests failing with sphinx dev version #1656
Comments
I fel on this issue in Sphinx tracker: sphinx-doc/sphinx#9841, could this be related to an incompatibility between |
Both my local setup and CI setup are using sphinx@1785fc93520cc7595f740f3270f715d17a67c7df and docutils 0.20.1 --- I'll try downgrading to 0.20.0 |
with 0.20.0 I still only see one warning:
|
ok I can repro locally (I forgot that the error was in pytest, not in build site). working on it... |
the problem, I think, is something to do with I suspect something along the lines of "the sphinx app is supposed to be a singleton and it's not" (which I saw mentioned in rstcheck/rstcheck#113). |
I changed Sphinx's own test set up recently (sphinx-doc/sphinx@462404c), would that be an impact? A |
indeed that commit is likely the problem. If I locally check out sphinx@841f2bd9b70e3559daf34c0d33210b1d24b621c1 (the immediately preceeding commit) then our tests pass. If I had to guess, I suspect it is the changes to |
temporary band-aid is pushed in f420c13 and it appears to have worked @12rambau note that I (perhaps callously) force-pushed to |
I've pushed sphinx-doc/sphinx@e3b613a, hopefully it serves as a fix? A |
our CI job running Sphinx 7.3.0 (current dev version) started failing today, like this:
Looks like probably (?) an upstream bug, but I haven't dug into it yet. Any takers?
The text was updated successfully, but these errors were encountered: