run-tests: allow bisecting a different repo
Add `--bisect-repo` flag which accepts a different repo to bisect.
3rd party extensions may reuse `run-tests.py` from core to run tests. Test
failure could be caused by either a core hg change or the 3rd party
extension code itself. Having a way to specify which repo to bisect is
useful.
Differential Revision: https://phab.mercurial-scm.org/D578
test-addremove.t
test-ancestor.py
test-backwards-remove.t
test-branch-tag-confict.t
test-casecollision.t
test-check-commit.t
test-check-execute.t
test-check-module-imports.t
test-check-pyflakes.t
test-check-pylint.t
test-check-shbang.t
test-contrib-check-code.t
test-contrib-check-commit.t
test-debugrename.t
test-diff-copy-depth.t
test-diff-hashes.t
test-diff-issue2761.t
test-diff-newlines.t
test-diff-reverse.t
test-diff-subdir.t
test-dirstate-nonnormalset.t
test-doctest.py
test-duplicateoptions.py
test-empty-dir.t
test-empty.t
test-encoding-func.py
test-excessive-merge.t
test-hghave.t
test-imports-checker.t
test-issue1089.t
test-issue1993.t
test-issue842.t
test-locate.t
test-lrucachedict.py
test-manifest.py
test-match.py
test-merge-default.t
test-merge2.t
test-merge5.t
test-permissions.t
test-push-checkheads-pruned-B1.t
test-push-checkheads-pruned-B6.t
test-push-checkheads-pruned-B7.t
test-push-checkheads-superceed-A1.t
test-push-checkheads-superceed-A4.t
test-push-checkheads-superceed-A5.t
test-push-checkheads-superceed-A8.t
test-push-checkheads-unpushed-D1.t
test-push-checkheads-unpushed-D6.t
test-push-checkheads-unpushed-D7.t
test-rename.t
test-revlog-packentry.t
test-run-tests.py
test-terse-status.t
test-unified-test.t
test-update-dest.t
test-update-reverse.t
test-xdg.t