Mercurial > hg
view tests/test-inotify-issue1556.t @ 15893:eb6867b98223
discovery: fix prepush documentation
The prepush documentation claim that when we refuse to push, the second element
of the returng tuple is an "outgoing" integer. value should be 0 when no
outgoing changeset and 1 otherwise. In pratice if there are no outgoing
changeset, "outgoing" value is alway 1 and util.Abort is raised on other error.
the stable branch also include this error so it wasn't introduced by a recent
refactoring.
author | Pierre-Yves David <pierre-yves.david@ens-lyon.org> |
---|---|
date | Fri, 13 Jan 2012 22:16:01 +0100 |
parents | 1f74b0d0f485 |
children | 895d65364570 |
line wrap: on
line source
$ "$TESTDIR/hghave" inotify || exit 80 $ hg init $ touch a b $ hg add a b $ rm b status without inotify $ hg st A a ! b $ echo "[extensions]" >> $HGRCPATH $ echo "inotify=" >> $HGRCPATH inserve $ hg inserve -d --pid-file=hg.pid 2>&1 $ cat hg.pid >> "$DAEMON_PIDS" status $ hg st A a ! b ? hg.pid $ sleep 1 Are we able to kill the service? if not, the service died on some error $ kill `cat hg.pid`