##// END OF EJS Templates
tests: use proctutil.stdout.write() instead of print() in test-extension.t...
tests: use proctutil.stdout.write() instead of print() in test-extension.t I was debugging this test failure on python3 + chg. I get the following hunk as test failure: ``` @@ -206,6 +206,18 @@ Check normal command's load order of ext 4) bar uipopulate 5) foo reposetup 5) bar reposetup + 4) foo uipopulate (chg !) + 4) bar uipopulate (chg !) + 4) foo uipopulate (chg !) + 4) bar uipopulate (chg !) + 4) foo uipopulate (chg !) + 4) bar uipopulate (chg !) + 4) foo uipopulate (chg !) + 4) bar uipopulate (chg !) + 4) foo uipopulate (chg !) + 4) bar uipopulate (chg !) + 5) foo reposetup (chg !) + 5) bar reposetup (chg !) 0:c24b9ac61126 ``` After hours of debugging and head scracthing, I figured out that something is wrong with output flushing. I initially switched the print() statements to ui.warn() but thanks to Yuya who suggested using procutil.stdout.write() instead.

File last commit:

r13383:70ef5b61 default
r45520:a28d1eca default
Show More
buildlocal.bat
9 lines | 267 B | application/x-msdownload | BatchLexer
@echo off
rem Double-click this file to (re)build Mercurial for Windows in place.
rem Useful for testing and development.
cd ..\..
del /Q mercurial\*.pyd
del /Q mercurial\*.pyc
rmdir /Q /S mercurial\locale
python setup.py build_py -c -d . build_ext -i build_mo
pause