Merge lp:~leonardr/launchpadlib/correct-test-failure into lp:launchpadlib
Status: | Merged |
---|---|
Merged at revision: | 105 |
Proposed branch: | lp:~leonardr/launchpadlib/correct-test-failure |
Merge into: | lp:launchpadlib |
Diff against target: |
40 lines (+9/-3) 3 files modified
src/launchpadlib/NEWS.txt (+6/-1) src/launchpadlib/__init__.py (+1/-1) src/launchpadlib/docs/introduction.txt (+2/-1) |
To merge this branch: | bzr merge lp:~leonardr/launchpadlib/correct-test-failure |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gary Poster | Approve | ||
j.c.sackett (community) | code* | Approve | |
Curtis Hovey | Pending | ||
Review via email: mp+45370@code.launchpad.net |
Description of the change
This branch corrects a test failure that doesn't show up locally or on an EC2 instance, but which does break buildbot. In introduction.txt, we call TestLaunchpad.
This is fine locally and on EC2, unless staging happens to be down. But code running on buildbot is prohibited from making external network requests, so the test fails with a cryptic httplib2 error.
I will do some more work on a more elegant solution, but simply changing the test should solve the problem. The login_anonymously() call is the only time we call one of the convenience methods of TestLaunchpad instead of using the constructor. (All the unit tests use NoNetworkLaunch
This looks good to me.