sapling/tests/test-dirstate-backup.t

Set up

  $ hg init repo
  $ cd repo

Try to import an empty patch

  $ hg import --no-commit - <<EOF
  > EOF
  applying patch from stdin
  abort: stdin: no diffs found
  [255]

No dirstate backups are left behind

  $ ls .hg/dirstate* | sort
  .hg/dirstate
tests: add a test demonstrating failure to clean up dirstate backups Differential Revision: https://phab.mercurial-scm.org/D1200 2017-10-20 15:53:33 +03:00			`Set up`

			`$ hg init repo`
			`$ cd repo`

			`Try to import an empty patch`

			`$ hg import --no-commit - <<EOF`
			`> EOF`
			`applying patch from stdin`
			`abort: stdin: no diffs found`
			`[255]`

dirstate: clean up when restoring identical backups When a dirstate backup is restored, it is possible that no actual changes to the dirstate have been made. In this case, the backup is still a hardlink to the original dirstate. Unfortunately, `os.rename` silently fails (nothing happens, and no error occurs) when `src` and `dst` are hardlinks to the same file. As a result, the backup is left lying around. Over time, these files accumulate. When restoring dirstate backups, check if the backup and the dirstate are the same file, and if so, just delete the backup. Differential Revision: https://phab.mercurial-scm.org/D1201 2017-10-20 15:53:35 +03:00			`No dirstate backups are left behind`
tests: add a test demonstrating failure to clean up dirstate backups Differential Revision: https://phab.mercurial-scm.org/D1200 2017-10-20 15:53:33 +03:00
			`$ ls .hg/dirstate* \| sort`
			`.hg/dirstate`