view tests/test-merge8.t @ 49991:3997c64eff8b

test: use a more direct approach to test racy mutation

The previous test was relying on implementation details and harder to maintain.

The new version is closer to the initial intend : "What happens the file get overwritten from under the current process"

This change is motivated by further changes around the transaction and dirstate
logic that would break the fragile equilibrium that existed before this patch.

Making this change early make it easier to review on its own and remove noise
in future larger changes.

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 ..