view tests/test-merge8.t @ 41152:191fac9ff9d3

obsutil: fix the issue5686

While traversing the obsolescence graph to find the successors sets
of csets:
    In its 4th case (read comments of obsutil.successorssets to see
    all 4 cases) where we know successors sets of all direct successors
    of CURRENT, we were just missing a condition to filter out the case
    when a cset is pruned.
    And without this condition (that this patch added) it was making a whole
    successor set to [] just because of one pruned marker.

For e.g:if following is the successors set of a cset A:
           A -> [a, b, c]

        if we prune c, we expect A's successors set to be [a, b] but
        you would get:
           A -> []
So this patch make sure that we calculate the right successorsset of csets
considering the pruned cset (in split case).

Differential Revision: https://phab.mercurial-scm.org/D5474

Test for changeset ba7c74081861
(update dirstate correctly for non-branchmerge updates)
  $ hg init a
  $ cd a
  $ echo a > a
  $ hg add a
  $ hg commit -m a
  $ cd ..
  $ hg clone a b
  updating to branch default
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ cd a
  $ hg mv a b
  $ hg commit -m move
  $ echo b >> b
  $ hg commit -m b
  $ cd ../b
  $ hg pull ../a
  pulling from ../a
  searching for changes
  adding changesets
  adding manifests
  adding file changes
  added 2 changesets with 2 changes to 1 files
  new changesets e3c9b40284e1:772b37f1ca37
  (run 'hg update' to get a working copy)
  $ hg update
  1 files updated, 0 files merged, 1 files removed, 0 files unresolved

  $ cd ..