tests: when making a `memctx`, make sure to use a single repo instance The way self.repo is dynamic produces bad lock behavior because the `context.memctx` ends up with a different instance than self in `localrepo.commitctx`, which means the callbacks in the `memctx` get an unlocked repo instance. This causes lock warning failures. When it's not a code freeze for core, we should probably: * Make lock failures hard, not just warnings * Stop holding a repo reference in memctx, or otherwise check it's the same instance as `self` during `localrepo.commitctx` That's my best guess based on the (very hard to debug) test failures here.

[tox]
envlist = hg37,hg38,hg39,hg40,hg41,hg42,hg43

[testenv]
deps=
    nose
    hg37: Mercurial==3.7.3
    hg38: Mercurial==3.8.3
    hg39: Mercurial==3.8.3
    hg40: Mercurial==4.0.2
    hg41: Mercurial==4.1.3
    hg42: Mercurial==4.2.2
    hg43: Mercurial==4.3.1
    subvertpy
commands=nosetests {posargs}