tests/failfilemerge.py

bundleoperation: optionnaly record the `remote` that produced the bundle

We have the information at hand, and the peer now have knownledge of its `path` object, which constaints useful behavior configuration.

So the simpler seems to be to pass that object around so it can be used if
needed.

# extension to emulate interrupting filemerge._filemerge


from mercurial import (
    error,
    extensions,
    filemerge,
)


def failfilemerge(*args, **kwargs):
    raise error.Abort(b"^C")


def extsetup(ui):
    extensions.wrapfunction(filemerge, 'filemerge', failfilemerge)