Mercurial > hg
view tests/test-profile @ 9694:8269fe2d48f6
hgweb: send proper error messages to the client
Fixes a bug in protocol which caused an exception during exception handling in
some cases on Windows. Also makes sure the server error message is correctly
propagated to the client, instead of being thrown away.
author | Sune Foldager <cryo@cyanite.org> |
---|---|
date | Mon, 02 Nov 2009 10:20:04 +0100 |
parents | 9a1b86cfd29e |
children |
line wrap: on
line source
#!/bin/sh echo % test --time hg --time help -q help 2>&1 | grep Time > /dev/null || echo --time failed hg init a cd a echo % test --profile if "$TESTDIR/hghave" -q lsprof; then hg --profile st 2>../out || echo --profile failed grep CallCount < ../out > /dev/null || echo wrong --profile hg --profile --config profiling.output=../out st 2>&1 \ || echo --profile + output to file failed grep CallCount < ../out > /dev/null \ || echo wrong --profile output when saving to a file hg --profile --config profiling.format=text st 2>&1 \ | grep CallCount > /dev/null || echo --profile format=text failed echo "[profiling]" >> $HGRCPATH echo "format=kcachegrind" >> $HGRCPATH hg --profile st 2>../out || echo --profile format=kcachegrind failed grep 'events: Ticks' < ../out > /dev/null || echo --profile output is wrong hg --profile --config profiling.output=../out st 2>&1 \ || echo --profile format=kcachegrind + output to file failed grep 'events: Ticks' < ../out > /dev/null \ || echo --profile output is wrong fi