Mercurial > hg
changeset 45155:a381618210d0
tests: test that push doesn’t complain about unstable changesets if no changes
When there’re no outgoing changes, push doesn’t complain about unstable
changesets.
There is currently a bug (see issue6372) that causes that there is an abort on
push when the outgoing changes contain another changeset even if that is not
obsolete or unstable. A test case and fix for that is sent in the next patch.
| author | Manuel Jacob <me@manueljacob.de> |
|---|---|
| date | Fri, 17 Jul 2020 07:59:20 +0200 |
| parents | 10f48720ef95 |
| children | c26335fa4225 |
| files | tests/test-obsolete.t |
| diffstat | 1 files changed, 20 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/tests/test-obsolete.t Fri Jul 17 03:53:19 2020 -0700 +++ b/tests/test-obsolete.t Fri Jul 17 07:59:20 2020 +0200 @@ -627,6 +627,26 @@ abort: push includes orphan changeset: cda648ca50f5! [255] +with --force it will work anyway + + $ hg push ../tmpc/ --force + pushing to ../tmpc/ + searching for changes + adding changesets + adding manifests + adding file changes + added 2 changesets with 2 changes to 2 files + 1 new obsolescence markers + 1 new orphan changesets + +if the orphan changeset is already on the server, pushing should work + + $ hg push ../tmpc/ + pushing to ../tmpc/ + searching for changes + no changes found + [1] + Test that extinct changeset are properly detected $ hg log -r 'extinct()'