-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Test suite appears to have a dependency on the user's global git config #11058
Comments
Mainly recording this for reference. I don't have time to look at fixing it now (or honestly, the motivation). As a workaround, I can use CI to run the full test suite for me. |
I took a quick look, those failures are all from relying implicitly that |
Thanks, that's roughly what I thought. I appreciate the confirmation. |
@pfmoore are you still running into this? I don't have a Windows setup to easily test unfortunately... |
I haven’t tried it recently. Isn’t |
It's not the default for git yet, no. I have it set to that user-wide ("global") on my Ubuntu system, but I strongly suspect whatever isolation issue you're running into is Windows specific... |
I'll try to confirm it's still an issue at some point. It's a long time since I ran the test suite locally, though (it's slow, and flaky, so I mostly rely on CI these days). |
No worries if you don't. At some point, I'll probably set up my Windows install for Python development and get around to investigating Windows specific issues. I have a reasonably fast laptop that run the test suite quickly. |
Description
I have
init.defaultbranch=main
in my git config, and a bunch of tests are failing withAssertionError: assert 'main' == 'master'
.I haven't looked in detail at these, but it looks like the global config is leaking into the tests.
Expected behavior
Test suite runs the same regardless of the user's configuration.
pip version
main branch
Python version
3.10
OS
Windows 11
How to Reproduce
Run the test suite with
init.defaultbranch=main
in your global git config. About 13 tests fail.Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: