Mercurial > evolve
view tests/test-single-head-obsolescence-named-branch-A1.t @ 6886:2540c03e1bf2 stable
tests: spell "sugar" correctly in test-tutorial.t
author | Anton Shestakov <av6@dwimlabs.net> |
---|---|
date | Wed, 02 Oct 2024 21:00:16 +0400 |
parents | ebc2dea354a2 |
children | b1d010b2e6c4 |
line wrap: on
line source
========================================= Testing single head enforcement: Case A-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 A: Involving obsolescence TestCase 1: A fully obsolete branch kept visible by another one. .. old-state: .. .. * 2 changesets on branch default .. * 2 changesets on branch double//slash on top of them. .. .. new-state: .. .. * 2 changesets on branch double//slash at the same location .. * 2 changesets on branch default superseding the other ones .. .. expected-result: .. .. * only one head detected .. .. graph-summary: .. .. D ● (branch double//slash) .. | .. C ● (branch double//slash) .. | .. B ø⇠◔ B' .. | | .. A ø⇠◔ A' .. |/ .. ● $ . $TESTDIR/testlib/topic_setup.sh $ . $TESTDIR/testlib/push-checkheads-util.sh Test setup ---------- $ mkdir A1 $ cd A1 $ 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 $ mkcommit B0 $ hg branch double//slash marked working directory as branch double//slash (branches are permanent and global, did you want a bookmark?) $ mkcommit C0 $ mkcommit D0 $ hg push --new-branch pushing to $TESTTMP/A1/server searching for changes adding changesets adding manifests adding file changes added 3 changesets with 3 changes to 3 files $ hg up 0 0 files updated, 0 files merged, 4 files removed, 0 files unresolved $ mkcommit A1 created new head (consider using topic for lightweight branches. See 'hg help topic') $ 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 @ 262c8c798096 [default] (draft): B1 | o f6082bc4ffef [default] (draft): A1 | | * ce55942d01c7 [double//slash] (draft): D0 | | | * 33628c681bad [double//slash] (draft): C0 | | | x d73caddc5533 [default] (draft): B0 | | | x 8aaa48160adc [default] (draft): A0 |/ o 1e4be0697311 [default] (public): root Actual testing -------------- $ hg push -r 'desc("B1")' pushing to $TESTTMP/A1/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