test_upgrade tests assume you can upgrade to format knit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Martin Pool |
Bug Description
When the default format is 2a, there are some failures where tests try to go from the default branch format to 'knit', which is no longer possible if the default is rich-root:
test: bzrlib.
failure: bzrlib.
RemoteException: Traceback (most recent call last):
File "/home/
['upgrade', '--format=knit', url])
AssertionError: Unexpected return code
not equal:
a = 0
b = 3
]
test: bzrlib.
failure: bzrlib.
RemoteException: Traceback (most recent call last):
File "/home/
self.
AssertionError: Unexpected return code
not equal:
a = 0
b = 3
]
Related branches
- Robert Collins (community): Approve
- Diff: 123 lines
Changed in bzr: | |
status: | Incomplete → In Progress |
assignee: | nobody → Martin Pool (mbp) |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
I suggest using 1.9-rich-root rather than knit; -or- hardcoding a starting format of 1.9, depending on the intent o f the individual tests.