buildroot/support/testing
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
..
conf support/testing: remove leftover kernel config fragment 2023-01-01 15:32:03 +01:00
infra support/tests: print failed command and output on assertRunOK error 2023-01-01 19:34:23 +01:00
tests support/testing/tests/package/test_gdb.py: drop version-specific tests 2022-11-03 23:08:10 +01:00
run-tests support/testing/run-tests: fix --testcases option 2022-07-27 18:20:44 +02:00