Mercurial > hg
comparison tests/test-obsolete.t @ 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 | 48b99af7b4b3 |
children | c26335fa4225 |
comparison
equal
deleted
inserted
replaced
45154:10f48720ef95 | 45155:a381618210d0 |
---|---|
624 $ hg push ../tmpc/ | 624 $ hg push ../tmpc/ |
625 pushing to ../tmpc/ | 625 pushing to ../tmpc/ |
626 searching for changes | 626 searching for changes |
627 abort: push includes orphan changeset: cda648ca50f5! | 627 abort: push includes orphan changeset: cda648ca50f5! |
628 [255] | 628 [255] |
629 | |
630 with --force it will work anyway | |
631 | |
632 $ hg push ../tmpc/ --force | |
633 pushing to ../tmpc/ | |
634 searching for changes | |
635 adding changesets | |
636 adding manifests | |
637 adding file changes | |
638 added 2 changesets with 2 changes to 2 files | |
639 1 new obsolescence markers | |
640 1 new orphan changesets | |
641 | |
642 if the orphan changeset is already on the server, pushing should work | |
643 | |
644 $ hg push ../tmpc/ | |
645 pushing to ../tmpc/ | |
646 searching for changes | |
647 no changes found | |
648 [1] | |
629 | 649 |
630 Test that extinct changeset are properly detected | 650 Test that extinct changeset are properly detected |
631 | 651 |
632 $ hg log -r 'extinct()' | 652 $ hg log -r 'extinct()' |
633 | 653 |