view tests/test-profile @ 12046:8e7960feb139 stable

Fix merge-tools.checkconflicts re.match only looks at the beginning of the merged file, and without re.MULTILINE the file had to end with ">>>>>>> something". Now conflict markers inside the file are found, too.
author Thomas Arendsen Hein <thomas@intevation.de>
date Thu, 26 Aug 2010 17:38:43 +0200
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