Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
TST: Add unit test to catch recurrences of #20822, #20855#20856
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
Note that the tests for this PR will be expected to fail until#20855 is merged. |
4df44f6
toa5da792
Comparea5da792
toe0ae4b0
Comparee0ae4b0
to79a0a33
CompareThis should pass now that#20855 has been merged. |
I cherry-picked this commit into#20857 for a belt-and-suspenders approach. |
Merged into#20857. |
Thanks@lpsinger ! I made the assumption you would not mind if we cherry-picked your commit to the other PR (and you are not counting merged PRs for a metric someplace), hope you are OK with this. |
Of course, no problem! |
PR Summary
Add a unit test to automatically catch issues like#20822 and#20855.
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).