mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git
synced 2026-01-26 14:13:24 +00:00
tests: disable libkbdfile testcase on ppc64el
Sometimes the libkbdfile-test13 fails on ppc64el with an error:
==19193== Command: /tmp/kbd/tests/libkbdfile/.libs/libkbdfile-test13
==19193==
vex: priv/host_ppc_defs.c:6712 (chainXDirect_PPC): Assertion `isLoadImm_EXACTLY2or5(p, 30, (Addr)disp_cp_chain_me_EXPECTED, mode64, endness_host)' failed.
vex storage: T total 275633592 bytes allocated
vex storage: P total 192 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
Thread 1: status = VgTs_Runnable (lwpid 19194)
==19194== at 0x48B6D44: memcpy (in /usr/libexec/valgrind/vgpreload_memcheck-ppc64le-linux.so)
==19194== by 0x49799B7: memcpy (string_fortified.h:29)
==19194== by 0x49799B7: __libc_sigaction (libc_sigaction.c:66)
==19194== by 0x4A7508B: __spawni_child (spawni.c:132)
==19194== by 0x4A99843: clone (clone.S:107)
client stack range: ??????? client SP: 0x492FB70
valgrind stack range: [0x1009260000 0x100935FFFF] top usage: 20464 of 1048576
Until we understand what the problem is and why the test _sometimes_
fails on this architecture, we will have to turn off the test.
Signed-off-by: Alexey Gladkov <legion@kernel.org>
This commit is contained in:
parent
c9debc0b77
commit
38e46e6b65
@ -62,6 +62,7 @@ AT_CLEANUP
|
||||
|
||||
AT_SETUP([test 13])
|
||||
AT_KEYWORDS([libkbdfile unittest])
|
||||
AT_SKIP_IF([ test "$(arch)" != "ppc64el" ])
|
||||
UNITTEST_MEMCHECK([$abs_builddir/libkbdfile/libkbdfile-test13])
|
||||
AT_CLEANUP
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ shift
|
||||
|
||||
case "$tool" in
|
||||
memcheck)
|
||||
valgrind_args="--leak-check=full --leak-resolution=high --show-leak-kinds=all --track-origins=yes"
|
||||
valgrind_args="--leak-check=full --leak-resolution=high --show-leak-kinds=all --track-origins=yes --trace-children=yes"
|
||||
;;
|
||||
*)
|
||||
echo >&1 "$0: unknown valgrind tool: $tool"
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user