view tests/test-issue522.t @ 49836:3d7bf111f01e stable

packaging: add dependencies to the PyOxidizer build on macOS

Otherwise, we get a bunch of test failures for missing things like pygments, or
tests skipped entirely.  The input file is a copy/paste from the equivalent
Windows file, but with dulwich, pygit2, and pytest-vcr commented out because
the build process errors out with them, flagging them as incompatible with
loading from memory.  I have no idea if that's actually true or not, because
I've noticed that if I don't `make clean` after every build, the next build
flags the watchman stuff as incompatible with loading from memory.

The remaining failures are:

    Failed test-alias.t: output changed
    Failed test-basic.t: output changed
    Failed test-check-help.t: output changed
    Failed test-commit-interactive.t: output changed
    Failed test-extension.t: output changed
    Failed test-help.t: output changed
    Failed test-i18n.t: output changed
    Failed test-log.t: output changed
    Failed test-qrecord.t: output changed
    Failed test-share-safe.t: output changed

Most of the issues seem related to loading help for disabled extensions from
`hgext.__index__`, namely the full extension help being unavailable, not being
able to resolve what commands are provided by what extension, and not having the
command level help available.

test-log.t, test-commit-interactive.t, and test-i18n.t look like i18n (or lack
thereof) issues.

test-basic.t is just odd:
    @@ -55,7 +55,7 @@
     On Python 3, stdio may be None:

       $ hg debuguiprompt --config ui.interactive=true 0<&-
    -   abort: Bad file descriptor (no-rhg !)
    +   abort: response expected
        abort: response expected (rhg !)
       [255]
       $ hg version -q 0<&-

https://bz.mercurial-scm.org/522

In the merge below, the file "foo" has the same contents in both
parents, but if we look at the file-level history, we'll notice that
the version in p1 is an ancestor of the version in p2. This test makes
sure that we'll use the version from p2 in the manifest of the merge
revision.

  $ hg init repo
  $ cd repo

  $ echo foo > foo
  $ hg ci -qAm 'add foo'

  $ echo bar >> foo
  $ hg ci -m 'change foo'

  $ hg backout -r tip -m 'backout changed foo'
  reverting foo
  changeset 2:4d9e78aaceee backs out changeset 1:b515023e500e

  $ hg up -C 0
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

  $ touch bar
  $ hg ci -qAm 'add bar'

  $ hg merge --debug
  resolving manifests
   branchmerge: True, force: False, partial: False
   ancestor: bbd179dfa0a7, local: 71766447bdbb+, remote: 4d9e78aaceee
   foo: remote is newer -> g
  getting foo
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)

  $ hg debugstate | grep foo
  m   0         -2 unset               foo

  $ hg st -A foo
  M foo

  $ hg ci -m 'merge'

  $ hg manifest --debug | grep foo
  c6fc755d7e68f49f880599da29f15add41f42f5a 644   foo

  $ hg debugindex foo
     rev linkrev       nodeid    p1-nodeid    p2-nodeid
       0       0 2ed2a3912a0b 000000000000 000000000000
       1       1 6f4310b00b9a 2ed2a3912a0b 000000000000
       2       2 c6fc755d7e68 6f4310b00b9a 000000000000