run-tests.py: don't let hg run interactively in debug mode stable
authorMads Kiilerich <madski@unity3d.com>
Fri, 18 Jan 2013 01:23:51 +0100
branchstable
changeset 1204 469ccfe7aa92
parent 1203 67fb241fb0b1
child 1205 531804688bf5
child 1206 9fb4b2c19bd8
run-tests.py: don't let hg run interactively in debug mode In normal test mode stdin is closed and hg is thus not interactive. In --debug mode stdin is inherited from the running console and to the tests, and hg could thus wait in prompts when running on Windows. See http://selenic.com/pipermail/mercurial-devel/2013-January/047548.html . Instead set ui.interactive=False to make Mercurial non-interactive. Other commands might still work differently in the --debug environment. This should solve the problem with hg waiting for input but still make it possible to add --debugger to hg in a test and run run-tests.py with --debug. [ original upstream message ]
tests/run-tests.py
--- a/tests/run-tests.py	Fri Jan 18 01:16:16 2013 +0100
+++ b/tests/run-tests.py	Fri Jan 18 01:23:51 2013 +0100
@@ -874,6 +874,7 @@
     hgrc = open(HGRCPATH, 'w+')
     hgrc.write('[ui]\n')
     hgrc.write('slash = True\n')
+    hgrc.write('interactive = False\n')
     hgrc.write('[defaults]\n')
     hgrc.write('backout = -d "0 0"\n')
     hgrc.write('commit = -d "0 0"\n')