test-ssh: do not actually look up "brokenrepository" by DNS
authorYuya Nishihara <yuya@tcha.org>
Sun, 26 Nov 2017 11:22:27 +0900
changeset 35180 3180ff7f6025
parent 35179 4abfe4169259
child 35181 d4805a5e7e70
test-ssh: do not actually look up "brokenrepository" by DNS
tests/test-ssh.t
--- a/tests/test-ssh.t	Thu Nov 23 01:21:10 2017 -0500
+++ b/tests/test-ssh.t	Sun Nov 26 11:22:27 2017 +0900
@@ -581,17 +581,16 @@
 
 abort with no error hint when there is a ssh problem when pulling
 
-  $ hg pull ssh://brokenrepository
+  $ hg pull ssh://brokenrepository -e "\"$PYTHON\" \"$TESTDIR/dummyssh\""
   pulling from ssh://brokenrepository/
-  remote: ssh: Could not resolve hostname brokenrepository: Name or service not known
   abort: no suitable response from remote hg!
   [255]
 
 abort with configured error hint when there is a ssh problem when pulling
 
-  $ hg pull ssh://brokenrepository --config ui.ssherrorhint="Please see http://company/internalwiki/ssh.html"
+  $ hg pull ssh://brokenrepository -e "\"$PYTHON\" \"$TESTDIR/dummyssh\"" \
+  > --config ui.ssherrorhint="Please see http://company/internalwiki/ssh.html"
   pulling from ssh://brokenrepository/
-  remote: ssh: Could not resolve hostname brokenrepository: Name or service not known
   abort: no suitable response from remote hg!
   (Please see http://company/internalwiki/ssh.html)
   [255]