Merge lp:~mars/launchpad/fix-ec2test-utf-in-devel into lp:launchpad
| Status: | Superseded |
|---|---|
| Proposed branch: | lp:~mars/launchpad/fix-ec2test-utf-in-devel |
| Merge into: | lp:launchpad |
| Diff against target: |
29 lines (+7/-4) 1 file modified
lib/devscripts/ec2test/tests/test_remote.py (+7/-4) |
| To merge this branch: | bzr merge lp:~mars/launchpad/fix-ec2test-utf-in-devel |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Leonard Richardson (community) | Approve on 2010-10-06 | ||
| Jonathan Lange (community) | 2010-10-06 | Needs Fixing on 2010-10-06 | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2010-10-06.
Description of the Change
Hi,
This branch fixes a problem on production-devel and Maverick local developer stations where a test would fail with a UTF-8 decoding error. This patch has already landed in production (see https:/
Maris
| Māris Fogels (mars) wrote : | # |
> Hey Mars,
>
> I think the right approach is to change get_body_text() to use decode=True
> itself. The point of the helper is to get the text.
>
> Also, strangely, these tests are failing for me in *stable*.
>
> jml
I saw this test failing for me in devel/Maverick, and in production-
I can fix the helper, but I also found that the reported TestResult changed if I did not do the calculations before the assertEquals() call. If the assertEquals() failed, then *its* TestResult would be used instead, to the great confusion of the developer.
I can change the helper.
| Māris Fogels (mars) wrote : | # |
Jono, does this fix look better?

Hey Mars,
I think the right approach is to change get_body_text() to use decode=True itself. The point of the helper is to get the text.
Also, strangely, these tests are failing for me in *stable*.
jml