Yann E. MORIN d475cb6056 support/tests: print failed command and output on assertRunOK error ... Currently, when asserting that a command succeeded, we just capture the return code of the command. If that is not zero, the assertion fails, but the error message is not very splicit: AssertionError: 1 != 0 Replace the error message with an explicit message that dumps the failed command, the error code, and the resulting output. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> (cherry picked from commit 44161560dd) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>		2023-01-01 19:34:23 +01:00
..
config-fragments	support/config-fragments/autobuild/bootlin-armv7m-uclibc.config: specify configuration more precisely	2022-09-17 14:45:47 +02:00
dependencies	support/dependencies: check for find and xargs	2022-08-21 15:50:15 +02:00
docker	support/docker: add shellcheck	2022-02-06 18:27:03 +01:00
download	support/download/cargo-post-process: cargo output for vendor config	2022-10-31 10:06:17 +01:00
gnuconfig	support/gnuconfig: fix previous version bump	2020-09-27 18:30:05 +02:00
kconfig	support/kconfig: fix compiler warnings	2021-10-06 21:11:09 +02:00
legal-info	boot, package, support, toolchain: switch to 2 spaces for the hash file	2022-07-28 23:05:23 +02:00
libtool
misc	Update for 2022.11	2022-12-05 08:23:19 +01:00
scripts	toolchain: support gconv modules from glibc >= 2.34	2022-10-21 21:02:40 +02:00
testing	support/tests: print failed command and output on assertRunOK error	2023-01-01 19:34:23 +01:00