| Message ID | 20221202163739.1194505-4-alex@linutronix.de |
|---|---|
| State | Accepted, archived |
| Commit | 9896fc1694c66d827383e385f1954d751b3e7c65 |
| Headers | show |
| Series | [1/4] ptest-packagelists.inc: correctly assign fast and slow tests | expand |
diff --git a/meta/conf/distro/include/ptest-packagelists.inc b/meta/conf/distro/include/ptest-packagelists.inc index 66b1fcbe3f..48dec07577 100644 --- a/meta/conf/distro/include/ptest-packagelists.inc +++ b/meta/conf/distro/include/ptest-packagelists.inc @@ -108,6 +108,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
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> --- meta/conf/distro/include/ptest-packagelists.inc | 2 ++ 1 file changed, 2 insertions(+)