summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKhem Raj <raj.khem@gmail.com>2024-01-10 23:05:37 -0800
committerKhem Raj <raj.khem@gmail.com>2024-01-12 09:08:26 -0800
commit36fe212db05bb26894c158053df0c5852084deb2 (patch)
treee392b3dcb78c4f948252a0f6a21a6e32e45c244e
parent0a5298f082e86341294c7d7d90acd11ccb0b6106 (diff)
downloadmeta-clang-36fe212db05bb26894c158053df0c5852084deb2.tar.gz
valgrind: Ignore some tests which fail with llvm/clang runtime
These tests could be fixed in valgrind if we did not treat linux == gcc assumption. On manual inspection, these tests are not really failing but clang based systems emit more information ( assembly file info in debug info) Signed-off-by: Khem Raj <raj.khem@gmail.com>
-rw-r--r--recipes-devtools/valgrind/valgrind_%.bbappend13
1 files changed, 13 insertions, 0 deletions
diff --git a/recipes-devtools/valgrind/valgrind_%.bbappend b/recipes-devtools/valgrind/valgrind_%.bbappend
new file mode 100644
index 0000000..d5c3d36
--- /dev/null
+++ b/recipes-devtools/valgrind/valgrind_%.bbappend
@@ -0,0 +1,13 @@
1
2# Remove tests when using clang since, clang generates debug info
3# for asm files too, like freebsd outputs but we are on linux
4# and valgrind tests think its always using gcc on linux
5do_install_ptest:append () {
6 if [ "${@bb.utils.contains('TC_CXX_RUNTIME', 'llvm', 'True', 'False', d)}" ]
7 then
8 rm ${D}${PTEST_PATH}/memcheck/tests/gone_abrt_xml.vgtest
9 rm ${D}${PTEST_PATH}/memcheck/tests/threadname_xml.vgtest
10 rm ${D}${PTEST_PATH}/drd/tests/annotate_barrier_xml.vgtest
11 rm ${D}${PTEST_PATH}/none/tests/fdleak_cmsg.vgtest
12 fi
13}