-
-
Notifications
You must be signed in to change notification settings - Fork 934
major test failures #673
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
Comments
It looks like it has something to do with the checkout on your machine, as it works fine on travis for example. |
I'm building using the pypi distfile with a simple |
I think in order to reproduce your local checkout, you would have to provide a script to clone this repository, probably along with the 'git' version used. The path it tries to use to access its own repository seems funny, and is probably the cause for this failure. Probably the tests are not made to be run under these conditions, possibly it's something that you can fix and provide a patch for? |
Perhaps I am misunderstanding something, but I do not provide or clone a repository. I just do the following:
and then I already see the errors cited before. |
I think it doesn't work because the source is not a git repository, which the tests expect. They perform read-only operations on the developers checkout. |
Ok, I understand. It would be good to disable the test target for the pypi tarball in some way then. (I think it would be possible to have a tarball with a repository as content for use in tests, instead of testing on the software's repository itself.) |
I am closing this issue as tests won't work without the GitPython git repository. See the related issue for another way to do this. |
When running the self tests for Gitpython-2.1.7 on NetBSD with python-3.6.2, ddt-1.1.1, mock-2.0.0, nose-1.3.7, smmap2-2.0.3, gitdb2-2.0.3 and git-2.14.2, not a single test succeeds:
gitdb2 has a number of test failures as well, see gitpython-developers/gitdb#42, but not on that scale.
The text was updated successfully, but these errors were encountered: