]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
ptest-packagelists.inc: do not run valgrind ptests on 32 bit x86
authorAlexander Kanavin <alex.kanavin@gmail.com>
Fri, 2 Dec 2022 16:37:39 +0000 (17:37 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 5 Dec 2022 22:28:10 +0000 (22:28 +0000)
Valgrind build itself with -mpreferred-stack-boundary=2 on that
target (and the tests expect that). On the other hand, we enable
SSE instructions, which expect things to be aligned on 16 byte
boundary (e.g. -mpreferred-stack-boundary=4). This won't be
reported at compile time and results in crashes at runtime, e.g.
vgdb simply does not work at all and crashes out immediately.
I am not sure how to resolve that, or whether we even should,
but the issue is reported here:
https://bugs.kde.org/show_bug.cgi?id=462553

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
meta/conf/distro/include/ptest-packagelists.inc

index cf1b57e1867e8282546bd037d19c013857dbf37a..79de9b00ae4da3439a541a3deabc767f4cec1cec 100644 (file)
@@ -109,6 +109,8 @@ PTESTS_SLOW = "\
 PTESTS_SLOW:remove:riscv64 = "valgrind-ptest"
 PTESTS_PROBLEMS:append:riscv64 = "valgrind-ptest"
 PTESTS_SLOW:append:libc-musl = " libc-test-ptest"
+PTESTS_SLOW:remove:x86 = "valgrind-ptest"
+PTESTS_PROBLEMS:append:x86 = "valgrind-ptest"
 
 #    ruby-ptest \ # Timeout
 #    lz4-ptest \ # Needs a rewrite