Merge lp:~gz/bzr/trivial_subunit_unexpectedly_correct into lp:bzr
Status: | Merged |
---|---|
Approved by: | Vincent Ladeuil |
Approved revision: | no longer in the source branch. |
Merged at revision: | 5898 |
Proposed branch: | lp:~gz/bzr/trivial_subunit_unexpectedly_correct |
Merge into: | lp:bzr |
Diff against target: |
20 lines (+7/-3) 1 file modified
bzrlib/tests/test_selftest.py (+7/-3) |
To merge this branch: | bzr merge lp:~gz/bzr/trivial_subunit_unexpectedly_correct |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Vincent Ladeuil | Approve | ||
Review via email: mp+61470@code.launchpad.net |
Commit message
Stop expecting subunit to get unexpected successes wrong if it has the recent fix.
Description of the change
Per bug 654474 subunit used to treat unexpected successes as successes rather than failures, and when John wrote some tests for logs being kept or discarded in subunit streams, he had to add an expectFailure for this case. Now that it's fixed in subunit (but not in a released version), that check unexpectedly passes with a trunk subunit. And as Bazaar now treats unexpected successes as failures too...
There doesn't seem to be a neat way of checking the subunit version, and we don't require a minimum subunit version for `bzr selftest` so this pokes around the subunit module to see if the new implementation is in place before running the check.
Hmm, should we file a bug to make sure we remove that once we require a released version of subunit with the fix ?
Half-serious.