On (19/05/14 20:34), Nikolai Kondrashov wrote:
On 05/19/2014 07:40 PM, Lukas Slebodnik wrote:
>On (19/05/14 18:15), Nikolai Kondrashov wrote:
>>Could you perhaps try timing the command running all tests under Valgrind,
>>which I mentioned in the previous message, if time allows?
>Sure,
>
>//parallel
>sh-4.2$ time make -j4 check LOG_COMPILER=libtool 'LOG_FLAGS=--mode=execute
valgrind --trace-children=yes --trace-children-skip=/* --leak-check=full'
>make check-recursive
> //snip
>real 0m47.355s
>user 1m46.597s
>sys 0m4.711s
>
>
>//single
>sh-4.2$ time make check LOG_COMPILER=libtool 'LOG_FLAGS=--mode=execute valgrind
--trace-children=yes --trace-children-skip=/* --leak-check=full'
>
>real 1m49.825s
>user 1m26.396s
>sys 0m4.228s
Thank you!
Wow, this runs really fast on your machine.
I'll have to investigate this, after all.
I found a reasoon why it is faster on my machine.
I was debugging crash in sbus_test, therefore I exported environment variable
CK_FORK=no. This is a reason why it is 4x faster.
export CK_FORK=no
time make check LOG_COMPILER=libtool 'LOG_FLAGS=--mode=execute valgrind
--trace-children=yes --trace-children-skip=/* --leak-check=full'
//snip
real 1m48.853s
user 1m25.409s
sys 0m4.146s
unset CK_FORK
time make check LOG_COMPILER=libtool 'LOG_FLAGS=--mode=execute valgrind
--trace-children=yes --trace-children-skip=/* --leak-check=full'
//snip
real 8m31.100s
user 7m49.765s
sys 0m21.273s
LS