|
From: Petar J. <mip...@gm...> - 2016-11-15 18:30:20
|
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 The previous patch was wrong, at least with the current DRD behaviour. Would the following one work for you? https://bugsfiles.kde.org/attachment.cgi?id=102247 bar_bad fails consistently on some systems and it would be good if we could find some solution for it. Regards, Petar |