]> code.ossystems Code Review - openembedded-core.git/commit
valgrind: adjust test filters and expected output
authorRandy MacLeod <Randy.MacLeod@windriver.com>
Tue, 14 May 2019 03:57:15 +0000 (23:57 -0400)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 15 May 2019 16:52:49 +0000 (17:52 +0100)
commit38cc663b69ec96ae1470f040f7dcb05e816deb2e
tree74bbe2a516535ccd82a51c650384f1472fa0f6cb
parenteb7d907deb09f2658f69d8faa8e56e6a56510fca
valgrind: adjust test filters and expected output

Skip two filters in filter_xml_frames since they
are intended to filter filesystem paths under '/usr' that
vary from platform to platform. In the ptest case
for Yocto's valgrind, the ptest executables are placed under:
   /usr/lib/valgrind/ptest
and if these frames are filtered out, then several 'drd' tests fail
the comparision between expected and actual output.

Also adjust the std_list expected output to agree with that
produced when the --yocto-ptest option to vg_regtest is used.

Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/valgrind/valgrind/0001-valgrind-filter_xml_frames-do-not-filter-usr.patch [new file with mode: 0644]
meta/recipes-devtools/valgrind/valgrind/0002-valgrind-adjust-std_list-expected-output.patch [new file with mode: 0644]
meta/recipes-devtools/valgrind/valgrind_3.15.0.bb