tests/blacklist

inotify: do not rely on stat(.hg/dirstate) to invalidate our dirstate

stat() is not reliable when several events happen quickly. Which means
that if two hg actions occur in the same second, stat() result will not
reflect the second change. And only _one_ invalidate() call was done.

Also ignore the events that occur when wlock is held, since wlock release
will trigger a full rescan anyway.

Fixes 17 run-tests.py --inotify tests.

# ConfigParser format
# Definitions of blacklists for run-tests.py
#
# Identify in config sections a list of tests you want to be skipped.
# Section names are meant to be used as targets for run-tests.py --blacklist
# option.
# "test-" prefixes should be omitted from test names. Values are not used.
#
# e.g. if your file looks like:
## [example]
## hgrc =
## help = "this string is not used"
# then calling "run-tests.py --blacklist example" will exclude test-hgrc and
# test-help from the list of tests to run.

[inotify-failures]
# When --inotify is activated, help output and config changes:
debugcomplete =
empty =
fncache =
globalopts =
help =
hgrc =
inherit-mode =
qrecord =
strict =

# --inotify activates de facto the inotify extension. It does not play well
# with inotify-specific tests, which activate/desactivate inotify at will:
inotify =
inotify-debuginotify =
inotify-dirty-dirstate =
inotify-issue1208 =
inotify-issue1371 =
inotify-issue1542 =
inotify-issue1556 =
inotify-lookup =