Mercurial > hg
comparison tests/run-tests.py @ 18449:20462259b92a
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.
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Fri, 18 Jan 2013 01:23:51 +0100 |
parents | e760414be201 |
children | f0124a65e8f8 |
comparison
equal
deleted
inserted
replaced
18448:e760414be201 | 18449:20462259b92a |
---|---|
872 | 872 |
873 # create a fresh hgrc | 873 # create a fresh hgrc |
874 hgrc = open(HGRCPATH, 'w+') | 874 hgrc = open(HGRCPATH, 'w+') |
875 hgrc.write('[ui]\n') | 875 hgrc.write('[ui]\n') |
876 hgrc.write('slash = True\n') | 876 hgrc.write('slash = True\n') |
877 hgrc.write('interactive = False\n') | |
877 hgrc.write('[defaults]\n') | 878 hgrc.write('[defaults]\n') |
878 hgrc.write('backout = -d "0 0"\n') | 879 hgrc.write('backout = -d "0 0"\n') |
879 hgrc.write('commit = -d "0 0"\n') | 880 hgrc.write('commit = -d "0 0"\n') |
880 hgrc.write('tag = -d "0 0"\n') | 881 hgrc.write('tag = -d "0 0"\n') |
881 if options.inotify: | 882 if options.inotify: |