Most of those tests are new in that revision; bzr-loom's branch implementation needs to be updated to match the new behaviour (i.e. fetch tagged revisions during pull and sprout). So in terms of end user functionality there's no regression there.
The bzrlib.plugins.loom tests that are failing are more of a concern, but probably a shallow issue of needing to be updated for the API changes documented in that revision:
* ``Branch.fetch`` implementations must now accept an optional
+ ``fetch_spec`` keyword argument. (Andrew Bennetts)
+
+* ``Branch.import_last_revision_info`` is deprecated. Use the
+ ``import_last_revision_info_and_tags`` method instead.
+ (Andrew Bennetts)
+
+* The ``revision_id`` parameter of
+ ``Repository.search_missing_revision_ids`` and
+ ``InterRepository.search_missing_revision_ids`` is deprecated. It is
+ replaced by the ``revision_ids`` parameter. (Andrew Bennetts)
Most of those tests are new in that revision; bzr-loom's branch implementation needs to be updated to match the new behaviour (i.e. fetch tagged revisions during pull and sprout). So in terms of end user functionality there's no regression there.
The bzrlib.plugins.loom tests that are failing are more of a concern, but probably a shallow issue of needing to be updated for the API changes documented in that revision:
* ``Branch.fetch`` implementations must now accept an optional import_ last_revision_ info`` is deprecated. Use the last_revision_ info_and_ tags`` method instead. search_ missing_ revision_ ids`` and ry.search_ missing_ revision_ ids`` is deprecated. It is
+ ``fetch_spec`` keyword argument. (Andrew Bennetts)
+
+* ``Branch.
+ ``import_
+ (Andrew Bennetts)
+
+* The ``revision_id`` parameter of
+ ``Repository.
+ ``InterReposito
+ replaced by the ``revision_ids`` parameter. (Andrew Bennetts)