annotate tests/test-ssh-repoerror.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<&-

#require unix-permissions no-root no-windows no-rhg

XXX-RHG this test hangs if `hg` is really `rhg`. This was hidden by the use of
`alias hg=rhg` by run-tests.py. With such alias removed, this test is revealed
buggy. This need to be resolved sooner than later.

repository itself is non-readable
---------------------------------

  $ hg init no-read
  $ hg id ssh://user@dummy/no-read
  000000000000
  $ chmod a-rx no-read

  $ hg id ssh://user@dummy/no-read
  remote: abort: Permission denied: *$TESTTMP/no-read/.hg* (glob)
  abort: no suitable response from remote hg
  [255]

special case files are visible, but unreadable
----------------------------------------------

This is "similar" to the test above, but the directory is "traversable". This
seems an unexpected case in real life, but we test it anyway.

  $ hg init other
  $ hg id ssh://user@dummy/other
  000000000000
  $ for item in `find other | sort -r` ; do
  >     chmod a-r $item
  > done

  $ hg id ssh://user@dummy/other
  remote: abort: Permission denied: '$TESTTMP/other/.hg/requires'
  abort: no suitable response from remote hg
  [255]

directory toward the repository is read only
--------------------------------------------

  $ mkdir deep
  $ hg init deep/nested

  $ hg id ssh://user@dummy/deep/nested
  000000000000

  $ chmod a-rx deep

  $ hg id ssh://user@dummy/deep/nested
  remote: abort: Permission denied: *$TESTTMP/deep/nested/.hg* (glob)
  abort: no suitable response from remote hg
  [255]

repository has wrong requirement
--------------------------------

  $ hg init repo-future
  $ hg id ssh://user@dummy/repo-future
  000000000000
  $ echo flying-car >> repo-future/.hg/requires
  $ hg id ssh://user@dummy/repo-future
  remote: abort: repository requires features unknown to this Mercurial: flying-car
  remote: (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
  abort: no suitable response from remote hg
  [255]