From patchwork Wed Oct  4 13:16:19 2017
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: D911: test-pager: make it compatible with chg
From: phabricator <phabricator@mercurial-scm.org>
X-Patchwork-Id: 24458
Message-Id: <657c0203e3684547c485df216486d3b5@localhost.localdomain>
To: mercurial-devel@mercurial-scm.org
Date: Wed, 4 Oct 2017 13:16:19 +0000

This revision was automatically updated to reflect the committed changes.
Closed by commit rHG73d8a5283f87: test-pager: make it compatible with chg (authored by quark, committed by ).

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST UPDATE
  https://phab.mercurial-scm.org/D911?vs=2366&id=2397

REVISION DETAIL
  https://phab.mercurial-scm.org/D911

AFFECTED FILES
  tests/test-pager.t

CHANGE DETAILS




To: quark, #hg-reviewers
Cc: mercurial-devel

diff --git a/tests/test-pager.t b/tests/test-pager.t
--- a/tests/test-pager.t
+++ b/tests/test-pager.t
@@ -195,6 +195,7 @@
   paged! 'summary:     modify a 8\n'
   paged! '\n'
 
+#if no-chg
 An invalid pager command name is reported sensibly if we don't have to
 use shell=True in the subprocess call:
   $ hg log --limit 3 --config pager.pager=this-command-better-never-exist
@@ -215,6 +216,17 @@
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     modify a 8
   
+#else
+Currently, chg has its own runpager implementation, which does not show the
+"missing pager" message. The error message is globed out since the shell could
+print different message.
+  $ hg log --limit 3 --config pager.pager=this-command-better-never-exist
+  /bin/sh: this-command-better-never-exist: command not found (?)
+  * (glob) (?)
+  killed!
+  [255]
+
+#endif
 
 A complicated pager command gets worse behavior. Bonus points if you can
 improve this.