##// END OF EJS Templates
run-tests.py: don't let hg run interactively in debug mode...
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.
Mads Kiilerich -
r18449:20462259 default
Show More
Name Size Modified Last Commit Author
/ contrib
hgfixes
hgsh
macosx
plan9
vim
win32
wix
bash_completion Loading ...
buildrpm Loading ...
casesmash.py Loading ...
check-code.py Loading ...
convert-repo Loading ...
debugcmdserver.py Loading ...
debugshell.py Loading ...
dumprevlog Loading ...
hg-ssh Loading ...
hgk Loading ...
hgweb.fcgi Loading ...
hgweb.wsgi Loading ...
lock-checker.py Loading ...
logo-droplets.svg Loading ...
memory.py Loading ...
mercurial.el Loading ...
mercurial.spec Loading ...
mergetools.hgrc Loading ...
mq.el Loading ...
perf.py Loading ...
pylintrc Loading ...
python-hook-examples.py Loading ...
sample.hgrc Loading ...
setup3k.py Loading ...
shrink-revlog.py Loading ...
simplemerge Loading ...
synthrepo.py Loading ...
tcsh_completion Loading ...
tcsh_completion_build.sh Loading ...
tmplrewrite.py Loading ...
undumprevlog Loading ...
xml.rnc Loading ...
zsh_completion Loading ...