##// END OF EJS Templates
Do not use osutil.c with python 2.4 and Windows (issue1364)...
Do not use osutil.c with python 2.4 and Windows (issue1364) Windows python 2.4 os.stat() reports times including DST offset, while osutil.c reports the correct value, which makes status() systematically compare files content. This bug is fixed in python 2.5. Using osutil.py instead of osutil.c is 4x times slower on large repositories but current code is completely unusable. Given few people are likely to use python 2.4 on Windows this solution was considered a good trade-off compared to more invasive solutions trying to address the offset issue.

File last commit:

r8024:9a1b86cf default
r10521:bde1bb25 stable
Show More
test-profile
32 lines | 1.1 KiB | text/plain | TextLexer
#!/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