comparison tests/test-largefiles-update.t @ 30190:56b930238036 stable

largefiles: more safe handling of interruptions while updating modifications

Largefiles are fragile with the design where dirstate and lfdirstate must be
kept in sync.

To be less fragile, mark all clean largefiles as unsure ("normallookup") before
updating standins. After standins have been updated and we know exactly which
largefile standins actually was changed, mark the unchanged largefiles back to
clean ("normal").

This will make the failure mode more safe. If interrupted, the next command
will continue to perform extra hashing of all largefiles. That will do that all
largefiles that are out of sync with their standin will be marked dirty and
they will show up in status and can be cleaned with update --clean.

30189:4999c12c526b

  $ hg status -A --rev tip large2
  C large2

#endif

Test a fatal error interrupting an update. lfdirstate doesn't realize that
.hglf has been updated while the largefile hasn't. Status thus shows a clean
state ... but rebuilding lfdirstate and checking all hashes reveals it isn't
clean.

Start with clean dirstates:
  $ hg up -qcr "8^"
  $ sleep 1
  $ hg st
Update standins without updating largefiles:
  $ cat << EOF > ../crashupdatelfiles.py
  > import hgext.largefiles.lfutil
  > def getlfilestoupdate(oldstandins, newstandins):
  >      raise SystemExit(7)
  > hgext.largefiles.lfutil.getlfilestoupdate = getlfilestoupdate
  > EOF
  $ hg up -Cr "8" --config extensions.crashupdatelfiles=../crashupdatelfiles.py
  [7]
Check large1 content and status:
BUG: largeX is R and large1 is not M and update does nothing
  $ cat large1
  large1 in #3
  $ hg st
  R largeX
  $ hg up -Cr .
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg st
  R largeX
Force largefiles rehashing and check again - revealing modifications that
update now can remove:
  $ rm .hg/largefiles/dirstate
  $ hg st
  M large1
  ! largeX
  $ hg up -Cr .
  getting changed largefiles
  2 largefiles updated, 0 removed
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg st
  $ cat large1
  manually modified before 'hg transplant --continue'

  $ cd ..

Test that "hg convert" avoids copying largefiles from the working
directory into store, because "hg convert" doesn't update largefiles

30190:56b930238036

  $ hg status -A --rev tip large2
  C large2

#endif

Test a fatal error interrupting an update. Verify that status report dirty
files correctly after an interrupted update. Also verify that checking all
hashes reveals it isn't clean.

Start with clean dirstates:
  $ hg up -qcr "8^"
  $ sleep 1
  $ hg st
Update standins without updating largefiles - large1 is modified and largeX is
added:
  $ cat << EOF > ../crashupdatelfiles.py
  > import hgext.largefiles.lfutil
  > def getlfilestoupdate(oldstandins, newstandins):
  >      raise SystemExit(7)
  > hgext.largefiles.lfutil.getlfilestoupdate = getlfilestoupdate
  > EOF
  $ hg up -Cr "8" --config extensions.crashupdatelfiles=../crashupdatelfiles.py
  [7]
Check large1 content and status ... and that update will undo modifications:
BUG: large is R
  $ cat large1
  large1 in #3
  $ hg st
  M large1
  R largeX
  $ hg up -Cr .
  getting changed largefiles
  1 largefiles updated, 0 removed
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ cat large1
  manually modified before 'hg transplant --continue'
  $ hg st
  R largeX
Force largefiles rehashing and check again - which makes it realize that largeX
not has been removed but just doesn't exist:
  $ rm .hg/largefiles/dirstate
  $ hg st
  ! largeX
  $ hg up -Cr .
  getting changed largefiles
  1 largefiles updated, 0 removed
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg st

  $ cd ..

Test that "hg convert" avoids copying largefiles from the working
directory into store, because "hg convert" doesn't update largefiles