Mercurial > hg
comparison tests/blacklists/fsmonitor @ 32769:efd6e941e933
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.
author | Siddharth Agarwal <sid0@fb.com> |
---|---|
date | Sat, 10 Jun 2017 14:07:30 -0700 |
parents | 3b67f27bb908 |
children | 0e2a6841ac5e |
comparison
equal
deleted
inserted
replaced
32768:483d47753726 | 32769:efd6e941e933 |
---|---|
1 # Blacklist for a full testsuite run with fsmonitor enabled. | 1 # Blacklist for a full testsuite run with fsmonitor enabled. |
2 # Use with | 2 # Used by fsmonitor-run-tests. |
3 # run-tests --blacklist=blacklists/fsmonitor \ | |
4 # --extra-config="extensions.fsmonitor=" | |
5 # The following tests all fail because they either use extensions that conflict | 3 # The following tests all fail because they either use extensions that conflict |
6 # with fsmonitor, use subrepositories, or don't anticipate the extra file in | 4 # with fsmonitor, use subrepositories, or don't anticipate the extra file in |
7 # the .hg directory that fsmonitor adds. | 5 # the .hg directory that fsmonitor adds. |
8 test-basic.t | 6 test-basic.t |
9 test-blackbox.t | 7 test-blackbox.t |