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_urllib2net fails #61362
Comments
test_urllib2net fails as follows. Looking at test_urllib2net.py" line 165 does not reveal anything interesting to me ./python Lib/test/regrtest.py -uall -v test_urllib2net ====================================================================== Traceback (most recent call last):
File "/glade/scratch/ddvento/build/Python-2.7.3-westmere/Lib/test/test_urllib2net.py", line 165, in test_urlwithfrag
"http://docs.python.org/glossary.html#glossary")
AssertionError: 'http://docs.python.org/2/glossary.html' != 'http://docs.python.org/glossary.html#glossary' Ran 15 tests in 14.684s FAILED (failures=1)
test test_urllib2net failed -- Traceback (most recent call last):
File "/glade/scratch/ddvento/build/Python-2.7.3-westmere/Lib/test/test_urllib2net.py", line 165, in test_urlwithfrag
"http://docs.python.org/glossary.html#glossary")
AssertionError: 'http://docs.python.org/2/glossary.html' != 'http://docs.python.org/glossary.html#glossary' 1 test failed: |
It passes on all our buildbots, and for me locally. Is it possible there is a proxy server between you and python.org that is changing the url returned? |
Yes, it is possible, do you want me to investigate more with my network |
I think only if you want to. As far as we are concerned the test is correct and passing. (And this kind of thing is the reason that that test set is only run when -uall is specified.) I'm going to close the issue. If you do investigate, and feel that you've found a real bug, please reopen it. |
The test is failing because of a restructuring of the docs.python.org website. The test was changed on 2012-10-28 to use the new URL (923ca6d73bad and friends). That change will be in the next set of maintenance releases including 2.7.4 real soon now. |
See also bpo-16969. |
Reopening, since this is still broken in Python 2.7.6 I wonder why do we have to use real websites instead of mocks for this test. And if there are really really really really good reasons, if we can use example.com instead as in issue bpo-20939 (maybe that is more stable than python.org) |
This was already fixed, just not before 2.7.6 was released. |
Actually, that's not quite right. It was fixed in 2.7.6, then changes to the website broke it again and it has been fixed again since then. Either way, it ain't broke right now ;) |
Well, ok, thanks :-) But I'm still wondering if it's not possible to use mocks for this test. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: