##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

run-tests: split tests/blacklist in tests/blacklists/*...
run-tests: split tests/blacklist in tests/blacklists/* 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
Nicolas Dumazet - - Load All Authors

File last commit:

r10300:c437745f default
r10300:c437745f default
Show More
inotify-failures
21 lines | 516 B | text/plain | TextLexer
/ tests / blacklists / inotify-failures
History | Annotation | Raw |Copy content |Copy permalink
# 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