-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
text builder: resolve an ordering conflict between two section-number-related tests #12868
text builder: resolve an ordering conflict between two section-number-related tests #12868
Conversation
Hum, why do we have this mypy failure? |
That's due to the issue reported in #12864, I think. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I didn't integrate the xdist feature yet, I'm ok with this.
Thank you Jay! |
Thanks @picnixz! That also reminds me to re-read your test framework pull requests again soon (I think they'll make more sense to me now with some improved understanding of the codebase). |
It's not really pressing. It's nice for the CI because we would make it run under a minute but we could hit other issues when used in production. But thank you for the suggestion! I will need to fix the conflicts before you review it again though. |
Feature or Bugfix
Purpose
test_build_text.test_secnums
andtest_build_text.test_nonascii_title_line
.Detail
test_nonascii_title_line
test needs a two-charactertext_add_secnumbers
configuration to pass successfully. Thetest_secnums
test can interfere with this if it runs first, because it modifies that configuration setting, and by default Sphinxenv
does not reload configuration values in-process after a build has already taken place.Relates
Edit(s): various attempts to improve the clarity of this pull request's description.