mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 01:39:21 +03:00
f6e8bdddc7
Following discussions with Gilles Morris [1], it seems that it is preferable to use several blacklist files in a blacklists/ directory. It is easier to add an unversioned file for experiments than modifying a tracked file. Also fall back to a simpler syntax, giving up ConfigParser, now that section names are not needed anymore. And allow --blacklist parameter to be a complete path, instead of only one of the filenames contained in tests/blacklists/ [1] http://www.selenic.com/pipermail/mercurial-devel/2009-December/017317.html |
||
---|---|---|
.. | ||
inotify-failures | ||
README |
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.