view tests/test-inotify-issue1542 @ 8335:713ec3f9c9de

inotify: Clarify the use of "watcher" name. Currently, Watcher is a class in inotify.linux.watcher, but it's also a class in inotify.server . To complicate things further more, the latter has a 'watcher' attribute, an instance of the former class. When it comes to the 'watcher' attribute of the Server class in inotify.server, one can get quite confused: is it a Watcher object from inotify.server, or from inotify.linux.watcher? Changes: * in inotify.linux.watcher : nothing * in inotify.server : ** Watcher class is renamed to RepoWatcher ** server.watcher is renamed to server.repowatcher
author Nicolas Dumazet <nicdumz.commits@gmail.com>
date Mon, 04 May 2009 21:18:33 +0900
parents 67e59a9886d5
children
line wrap: on
line source

#!/bin/sh

"$TESTDIR/hghave" inotify || exit 80

hg init

touch a
mkdir dir
touch dir/b
touch dir/c

echo "[extensions]" >> $HGRCPATH
echo "inotify=" >> $HGRCPATH

hg add dir/c

echo % inserve
hg inserve -d --pid-file=hg.pid 2>&1
cat hg.pid >> "$DAEMON_PIDS"

hg st

echo % moving dir out
mv dir ../tmp-test-inotify-issue1542

echo % status
hg st

sleep 1
echo "Are we able to kill the service? if not, the service died on some error"
kill `cat hg.pid`