view tests/test-update-issue1456.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

#require execbit

  $ rm -rf a
  $ hg init a
  $ cd a

  $ echo foo > foo
  $ hg ci -qAm0
  $ echo toremove > toremove
  $ echo todelete > todelete
  $ chmod +x foo toremove todelete
  $ hg ci -qAm1

Test that local removed/deleted, remote removed works with flags
  $ hg rm toremove
  $ rm todelete
  $ hg co -q 0

  $ echo dirty > foo
  $ hg up -c
  abort: uncommitted changes
  [255]
  $ hg up -q
  $ cat foo
  dirty
  $ hg st -A
  M foo
  C todelete
  C toremove

Validate update of standalone execute bit change:

  $ hg up -C 0
  1 files updated, 0 files merged, 2 files removed, 0 files unresolved
  $ chmod -x foo
  $ hg ci -m removeexec
  nothing changed
  [1]
  $ hg up -C 0
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg up
  3 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg st

  $ cd ..