view tests/test-narrow-debugrebuilddirstate.t @ 49510:e02dcc625171

revset: handle wdir() in `roots()`

This is already handled in `heads()`, and both are needed to determine if a set
is contiguous.

I'm guessing the `0 <= p` check was to try to filter out the null revision, but
it looks like that comes through in the corner case of a new repo with no
commits.  But that was already the case, as shown by the tests.

Before (on a clone of hg):

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059301 comb 0.040000 user 0.040000 sys 0.000000 (best of 100)

After:

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059387 comb 0.060000 user 0.060000 sys 0.000000 (best of 100)

  $ . "$TESTDIR/narrow-library.sh"
  $ hg init master
  $ cd master
  $ echo treemanifest >> .hg/requires
  $ echo 'contents of file' > file
  $ mkdir foo
  $ echo 'contents of foo/bar' > foo/bar
  $ hg ci -Am 'some change'
  adding file
  adding foo/bar

  $ cd ..
  $ hg clone --narrow ssh://user@dummy/master copy --include=foo
  requesting all changes
  adding changesets
  adding manifests
  adding file changes
  added 1 changesets with 1 changes to 1 files
  new changesets * (glob)
  updating to branch default
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ cd copy

  $ hg debugdirstate --no-dates
  n *         20 *               foo/bar (glob)
  $ mv .hg/dirstate .hg/old_dirstate
  $ dd bs=40 count=1 if=.hg/old_dirstate of=.hg/dirstate 2>/dev/null
  $ hg debugdirstate
  $ hg debugrebuilddirstate
  $ hg debugdirstate
  n *         * unset               foo/bar (glob)