tests/.balto.toml

setup: avoid attempting to invoke the system-wide hg.exe on Windows

On Windows, the executable in the current directory gets priority over anything
in $PATH (both for cmd.exe and MSYS).  That means, the former code was launching
the local hg.exe instead of the system-wide one, if it was previously built.  If
that failed, it then fell back to the local hg code, but run through python.exe.

I'm not sure what it is about ef7119cd4965, but that started throwing up a
messagebox that python37.dll couldn't be loaded.  (And indeed, python37 is not
in $PATH by default.)  Invoking the local hg via the current python avoids that.

# Balto (https://bitbucket.org/lothiraldan/balto/src) is a test orchestrator
# which is compatible with all test runner that can emit the LITF
# (https://github.com/lothiraldan/litf) test format.

# The plugin for the Mercurial test runner is mercurial-litf
# (https://pypi.org/project/mercurial-litf/). Make sure to follow the
# instruction and configuration instructions here:
# https://bitbucket.org/lothiraldan/mercurial_litf/src/default/

# You can launch Balto with `balto /path/to/mercurial/tests/`

name = "Mercurial Test Suite"
tool = "mercurial"