sparse: remove the failed attempt to change watchman config during test

Summary:
I've seen the failures like https://phabricator.intern.facebook.com/P56599278
which were the result of "enforce_root_files" being set in our global watchman
config.

It appears that the global configs are being picked up only on server start.
Killing server during the test won't help because watchman is automagically
restarted in our dev environment.

The way to do it properly is to mimic
https://github.com/facebook/watchman/blob/master/tests/integration/WatchmanInstance.py
until we do that I've just put a .watchmanconfig to fix the test.

Test Plan: tests is passing now

Reviewers: #mercurial, ttung, durham, wez, zamsden

Reviewed By: wez, zamsden

Subscribers: mjpieters

Differential Revision: https://phabricator.intern.facebook.com/D3772968

Signature: t1:3772968:1472158987:0e08c5e9f862ba3d74d016d051b852512d06e399
This commit is contained in:
Mateusz Kwapich 2016-08-26 11:59:52 -07:00
parent 8bc273e058
commit dd16a02f8e

View File

@ -24,10 +24,10 @@ Test integration with simplecache for profile reads
got value for key sparseprofile:.hgsparse:52fe6c0958d7d08df53bdf7ee62a261abb7f599e:v1 from local
Test fsmonitor integration (if available)
(disable the system watchman config)
$ export WATCHMAN_CONFIG_FILE
$ WATCHMAN_CONFIG_FILE=/dev/null
TODO: make fully isolated integration test a'la https://github.com/facebook/watchman/blob/master/tests/integration/WatchmanInstance.py
(this one is using the systemwide watchman instance)
$ touch .watchmanconfig
$ $PYTHON -c 'import hgext.fsmonitor' || exit 80
$ echo "ignoredir1/" >> .hgignore
$ hg commit -Am ignoredir1