mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 08:18:15 +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
22 lines
516 B
Plaintext
22 lines
516 B
Plaintext
# When --inotify is activated, help output and config changes:
|
|
test-debugcomplete
|
|
test-empty
|
|
test-fncache
|
|
test-globalopts
|
|
test-help
|
|
test-hgrc
|
|
test-inherit-mode
|
|
test-qrecord
|
|
test-strict
|
|
|
|
# --inotify activates de facto the inotify extension. It does not play well
|
|
# with inotify-specific tests, which activate/desactivate inotify at will:
|
|
test-inotify
|
|
test-inotify-debuginotify
|
|
test-inotify-dirty-dirstate
|
|
test-inotify-issue1208
|
|
test-inotify-issue1371
|
|
test-inotify-issue1542
|
|
test-inotify-issue1556
|
|
test-inotify-lookup
|