-
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
Mark tests using remote svn and hg as xfail #8790
Conversation
7611e57
to
51d77e6
Compare
Maybe we should just drop these tests? I'm not sure that svn support is that important for open source any more, and if corporate users want us to keep the tests, maybe they could donate a public-facing svn instance we could test against? (Note: I'm not saying we drop support for subversion, that's a different question) |
I will modify this PR to drop these tests then.
|
@McSinyx maybe you need update the title of this PR. |
Thanks for the heads up! In other news BitBucket stops supporting Mercurial )-: |
@@ -58,7 +56,8 @@ def test_install_subversion_usersite_editable_with_distribute( | |||
'install', '--user', '-e', | |||
'{checkout}#egg=initools'.format( | |||
checkout=local_checkout( | |||
'svn+http://svn.colorstudy.com/INITools', tmpdir) | |||
'git+https://github.com/ianb/initools', tmpdir, | |||
) |
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.
Seems wrong to use git for a test named test_install_subversion_usersite_editable_with_distribute
. Are these not tests specifically designed to test subversion features?
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.
I renamed the test to test_install_git_usersite_editable_with_distribute
now. It seems to be the only test doing editable install for user and subversion was used for historical reasons.
They've been warning that was coming for months. In fact, I thought it had happened ages ago. |
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.
Maybe you could fix here test_install_global_option_using_editable? that is also fail
The BitBucket repo doesn't drop hg support (yet), but now requires authentication. I suppose for now it's OK to replace it with another one even it's git instead. Edit: BitBucket really dropped hg support. |
I honestly have no idea if it's OK to switch from svn/hg to git for these tests. So I'm going to defer to other @pypa/pip-committers on whether to merge this. |
Instead of switching away from SVN, maybe we should initialise an SVN repository locally, and access it with |
Which reminds me that we'd be blocked by this packaging issue: pypa/packaging#264 |
IMHO, we should mark those tests as xfail because we are blocking all new PR. Also master will fail? |
I agree, that feels like the best we can do before packaging is updated to allow |
0c764ba
to
d429b39
Compare
I marked all tests using svn.colorstudy.com as xfailed now. I just want to note that though I don't understand what the svn helper is doing: Lines 17 to 37 in e1d489f
It seems that a regular svn checkout, e.g. from https://github.com/ianb/INITools, won't just work, and that the dump file is no longer accessible due to BitBucket support for the repo (which was managed by hg) is now retired. |
The source repositories for testing is no longer available.
I think we’ll need an admin to do this by hand since both this and #8791 fail some required checks and can’t be merged automatically. |
Not just by hand, one of us needs to go and disable certain protections to be able to make these merges. :) |
Thanks. I don't know who are admins and at this point I'm too afraid to ask. |
I've just migrated a repo to https://hg.sr.ht/~cnx/lazip, to be used in the future if we ever want to test installing from mercurial again. |
colorstudy.com has been down for a few days now. TBH I'm not sure how long will GitHub keep supporting SVN checkouts, but for the moment I think it is OK.
Edit: This doesn't seem to work. Is it OK to mark the 4 subversion tests as xfail?