Mercurial > evolve
view tests/test-single-head-obsolescence-topic-B1.t @ 6223:4298ae0b966d stable
evolve: don't update wdir when --dry-run is given (issue6669)
What _cleanup() should've been called, perhaps, is _update(). Because it
updates working copy to either headnode or a successor of startnode. And yes,
it performs an update even when shouldupdate is False. So when --dry-run is
given, we should simply avoid calling _cleanup().
author | Anton Shestakov <av6@dwimlabs.net> |
---|---|
date | Sat, 09 Apr 2022 20:49:43 +0300 |
parents | 8cc7732a29bf |
children | d1a6d83a7109 |
line wrap: on
line source
========================================= Testing single head enforcement: Case B-1 ========================================= A repository is set to only accept a single head per name (typically named branch). However, obsolete changesets can make this enforcement more complicated, because they can be kept visible by other changeset on other branch. This case is part of a series of tests checking this behavior. Category B: Involving obsolescence with topic TestCase 1: A fully obsolete topic kept visible by another one. .. old-state: .. .. * 2 changesets on topic X .. * 2 changesets on topic Y on top of them. .. .. new-state: .. .. * 2 changesets on topic Y at the same location .. * 2 changesets on topic X superseding the other ones .. .. expected-result: .. .. * only one head detected .. .. graph-summary: .. .. D ● (topic-Y) .. | .. C ● (topic-Y) .. | .. B ø⇠◔ B' (topic-X) .. | | .. A ø⇠◔ A' (topic-X) .. |/ .. ● $ . $TESTDIR/testlib/topic_setup.sh $ . $TESTDIR/testlib/push-checkheads-util.sh Test setup ---------- $ mkdir B1 $ cd B1 $ setuprepos single-head creating basic server and client repo updating to branch default 2 files updated, 0 files merged, 0 files removed, 0 files unresolved $ cd client $ hg topic -r . topic-X switching to topic topic-X changed topic on 1 changesets to "topic-X" $ hg strip --config extensions.strip= --hidden 'hidden()' --no-backup # clean old A0 $ mkcommit B0 $ hg topic topic-Y $ mkcommit C0 active topic 'topic-Y' grew its first changeset (see 'hg help topics' for more information) $ mkcommit D0 $ hg push --new-branch pushing to $TESTTMP/B1/server searching for changes adding changesets adding manifests adding file changes added 4 changesets with 3 changes to 4 files (+1 heads) 1 new obsolescence markers obsoleted 1 changesets $ hg up 0 0 files updated, 0 files merged, 4 files removed, 0 files unresolved $ hg topic topic-X marked working directory as topic: topic-X $ mkcommit A1 $ mkcommit B1 $ hg debugobsolete `getid "desc(A0)"` `getid "desc(A1)"` 1 new obsolescence markers obsoleted 1 changesets 3 new orphan changesets $ hg debugobsolete `getid "desc(B0)"` `getid "desc(B1)"` 1 new obsolescence markers obsoleted 1 changesets $ hg log -G --hidden @ f4ed6717fb66 [default:topic-X] (draft): B1 | o c1340bef453e [default:topic-X] (draft): A1 | | * 618812b710f7 [default:topic-Y] (draft): D0 | | | * d1ad53773db2 [default:topic-Y] (draft): C0 | | | x 1c1f62b56685 [default:topic-X] (draft): B0 | | | x 5a47a98cd8e5 [default:topic-X] (draft): A0 |/ o 1e4be0697311 [default] (public): root Actual testing -------------- $ hg push -r 'desc("B1")' pushing to $TESTTMP/B1/server searching for changes adding changesets adding manifests adding file changes added 2 changesets with 2 changes to 2 files (+1 heads) 2 new obsolescence markers obsoleted 2 changesets 2 new orphan changesets