view tests/test-changelog-exec.t @ 37772:814151cd8c4a

logcmdutil: rewrite jsonchangeset printer to be backed by jsonformatter

This is a bit slower than the original implementation, but I don't think
that would actually matter. It's still faster than full templating.

  $ hg log -Tjson -r0:5000 --time > /dev/null
  (orig) time: real 1.550 secs (user 1.500+0.000 sys 0.040+0.000)
  (new)  time: real 1.810 secs (user 1.740+0.000 sys 0.070+0.000)

  cf.
  $ hg log -Tdefault -r0:5000 --time > /dev/null
  time: real 4.980 secs (user 4.850+0.000 sys 0.130+0.000)
  $ hg log -r0:5000 --time > /dev/null
  time: real 2.340 secs (user 2.220+0.000 sys 0.100+0.000)
  $ hg log -r0:5000 -q --time > /dev/null
  time: real 0.750 secs (user 0.670+0.000 sys 0.070+0.000)

The test output changes because keys are sorted alphabetically.

#require execbit

b51a8138292a introduced a regression where we would mention in the
changelog executable files added by the second parent of a merge. Test
that that doesn't happen anymore

  $ hg init repo
  $ cd repo
  $ echo foo > foo
  $ hg ci -qAm 'add foo'

  $ echo bar > bar
  $ chmod +x bar
  $ hg ci -qAm 'add bar'

manifest of p2:

  $ hg manifest
  bar
  foo

  $ hg up -qC 0
  $ echo >> foo
  $ hg ci -m 'change foo'
  created new head

manifest of p1:

  $ hg manifest
  foo

  $ hg merge
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)
  $ chmod +x foo
  $ hg ci -m 'merge'

this should not mention bar but should mention foo:

  $ hg tip -v
  changeset:   3:c53d17ff3380
  tag:         tip
  parent:      2:ed1b79f46b9a
  parent:      1:d394a8db219b
  user:        test
  date:        Thu Jan 01 00:00:00 1970 +0000
  files:       foo
  description:
  merge
  
  

  $ hg debugindex bar
     rev linkrev nodeid       p1           p2
       0       1 b004912a8510 000000000000 000000000000

  $ cd ..