tests: use the system hg for examining the local repository Most test scripts use "hg" to interact with a temporary test repository. However a few tests also want to run hg commands to interact with the local repository containing the mercurial source code. Notably, many of the test-check-* tests want to check local files and commit messages. These tests were previously using the version of hg being tested to query the source repository. However, this will fail if the source repository requires extensions or other settings not supported by the version of mercurial being tested. The source repository was typically initially cloned using the system hg installation, so we should use the system hg installation to query it. There was already a helpers-testrepo.sh script designed to help cope with different requirements for the source repository versus the test repositories. However, it only handled the evolve extension. This new behavior works with any extensions that are different between the system installation and the test installation.

     1

#require test-repo pyflakes hg10

     2

     3

  $ . "$TESTDIR/helpers-testrepo.sh"

     4

  $ cd "`dirname "$TESTDIR"`"

     5

     6

run pyflakes on all tracked files ending in .py or without a file ending

     7

(skipping binary file random-seed)

     8

     9

  $ syshg locate 'set:**.py or grep("^#!.*python")' \

    10

  > -X hgext/fsmonitor/pywatchman \

    11

  > -X mercurial/pycompat.py -X contrib/python-zstandard \

    12

  > 2>/dev/null \

    13

  > | xargs pyflakes 2>/dev/null | "$TESTDIR/filterpyflakes.py"

    14

  tests/filterpyflakes.py:41: undefined name 'undefinedname'

    15