sapling/tests/blacklists
Siddharth Agarwal a90fb2f356 tests: add a wrapper to run fsmonitor tests
This script does a bunch of non-trivial configuration work: in particular, it
sets up an isolated instance of Watchman which isn't affected by global state
and can be torn down on completion.

This script also sets the HGFSMONITOR_TESTS environment variable, which hghave
will use in the next patch to allow gating on whether fsmonitor is enabled.

With fsmonitor enabled, there appear to be a number of failures in the test
suite. It's not yet clear to me why they're happening, but if someone would
like to jump in and fix some of them I hope this will be helpful for that.
2017-06-10 14:07:30 -07:00
..
fsmonitor tests: add a wrapper to run fsmonitor tests 2017-06-10 14:07:30 -07:00
linux-vfat extensions: remove the inotify extension (BC) 2014-03-01 16:20:15 -06:00
README run-tests: split tests/blacklist in tests/blacklists/* 2009-12-10 17:21:31 +09:00

Put here definitions of blacklists for run-tests.py

Create a file per blacklist. Each file should list the names of tests that you
want to be skipped.
File names are meant to be used as targets for run-tests.py --blacklist
option.
Lines starting with # are ignored. White spaces are stripped.

e.g. if you create a blacklist/example file containing:
 test-hgrc
 # some comment
 test-help
then calling "run-tests.py --blacklist blacklists/example" will exclude
test-hgrc and test-help from the list of tests to run.