Mercurial > hg
view tests/test-inotify-issue1371.t @ 19406:3185b347ae98
worker: check problem state correctly (issue3982)
If a large update triggered an abort, it was possible for the main
thread to still update the dirstate.
This fix is incomplete, as the failing worker now doesn't generate a
proper error message. This is difficult in the fork-based framework,
which relies on exceptions propagating to the top of the dispatcher
for formatting.
author | Matt Mackall <mpm@selenic.com> |
---|---|
date | Tue, 16 Jul 2013 11:53:53 -0500 |
parents | f58175f409b0 |
children |
line wrap: on
line source
$ "$TESTDIR/hghave" inotify || exit 80 $ hg init $ touch a b c d e f $ echo "[extensions]" >> $HGRCPATH $ echo "inotify=" >> $HGRCPATH inserve $ hg inserve -d --pid-file=hg.pid 2>&1 $ cat hg.pid >> "$DAEMON_PIDS" $ hg ci -Am m adding a adding b adding c adding d adding e adding f adding hg.pid let the daemon finish its stuff $ sleep 1 eed to test all file operations $ hg rm a $ rm b $ echo c >> c $ touch g $ hg add g $ hg mv e h $ hg status M c A g A h R a R e ! b $ sleep 1 Are we able to kill the service? if not, the service died on some error $ "$TESTDIR/killdaemons.py" hg.pid