Mercurial > evolve
view tests/test-next-abort.t @ 6197:f1d4c9eddcc1
tests: use desc() revset instead of node hashes in test-evolve-continue.t
Using desc() makes the tests less fragile if new steps are inserted, since the
test output can be more easily regenerated rather than having to go and find
all of the commit hashes in the input to replace them.
author | Luke Granger-Brown <hg@lukegb.com> |
---|---|
date | Mon, 14 Mar 2022 17:05:41 +0000 |
parents | ed68f64f5d0f |
children | e6ae5af97683 889d21445ee9 |
line wrap: on
line source
Testing hg next with --abort flag and hg abort command handling an interrupted hg next $ . "$TESTDIR/testlib/common.sh" $ cat >> "$HGRCPATH" << EOF > [extensions] > evolve = > EOF $ hg init next-abort $ cd next-abort $ echo apple > a $ hg ci -qAm apple $ echo banana > b $ hg ci -qAm banana $ hg up 0 0 files updated, 0 files merged, 1 files removed, 0 files unresolved $ echo blueberry > b $ hg ci -qAm 'apple and blueberry' --amend 1 new orphan changesets $ hg next move:[1] banana atop:[2] apple and blueberry merging b warning: conflicts while merging b! (edit, then use 'hg resolve --mark') unresolved merge conflicts (see 'hg help evolve.interrupted') [240] #testcases abortcommand abortflag #if abortflag $ hg next --abort next aborted working directory is now at 1c7f51cf0ef0 $ hg next --abort abort: no interrupted next to abort [255] $ hg evolve --abort abort: no interrupted evolve to abort [255] $ hg next --abort --move-bookmark abort: cannot specify both --abort and --move-bookmark [10] $ hg next --abort --merge abort: cannot specify both --abort and --merge [10] #else $ hg abort --dry-run evolve in progress, will be aborted $ hg abort evolve aborted working directory is now at 1c7f51cf0ef0 $ hg abort abort: no operation in progress [20] #endif $ cd ..