|
From: Philippe W. <phi...@sk...> - 2016-11-17 22:09:28
|
On Tue, 2016-11-15 at 19:30 +0100, Petar Jovanovic wrote: > Hi Philippe, > > > * helgrind test seems to succeed (more?) systematically, but takes a > lot > > longer (around one minute, burning a lot of CPU, against about 10 > > seconds unpatched). > > This is a bit unusual. I have seen awfully long executions with the > current > trunk (i.e. without any patches) on my multicore x86 server ( > Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz). > > $ time perl tests/vg_regtest helgrind/tests/bar_bad.vgtest > bar_bad: valgrind -q ./bar_bad > > == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > > > real 19m57.592s > user 20m5.572s > sys 0m1.680s I think these (sometimes) very long execution times are due to the default (unfair) way the valgrind scheduler works, which might cause starvation. Adding options --fair-sched=try for the 3 */tests/bar_bad*vgtest should ensure a reasonable bounded time. Philippe |