qemu/tests/functional/qemu_test
Daniel P. Berrangé 6f0942b723 tests/functional: logs details of console interaction operations
When functional tests go wrong, it will often be related to the console
interaction wait state. By logging the messages that we're looking for,
and data we're about to be sending, it'll be easier to diagnose where
tests are getting stuck.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20241121154218.1423005-13-berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20241121165806.476008-13-alex.bennee@linaro.org>
2024-11-25 10:13:41 +00:00
..
__init__.py tests/functional: Add the LinuxKernelTest for testing the Linux boot process 2024-09-11 09:49:11 +02:00
asset.py tests/functional: make cached asset files read-only 2024-11-04 14:16:11 +01:00
cmd.py tests/functional: logs details of console interaction operations 2024-11-25 10:13:41 +00:00
config.py tests/functional: Add base classes for the upcoming pytest-based tests 2024-09-04 10:52:29 +02:00
linuxkernel.py tests/functional/qemu_test: Add a function for launching kernels more easily 2024-09-24 13:38:29 +02:00
tesseract.py tests/functional: Fix bad usage of has_cmd 2024-09-11 09:49:12 +02:00
testcase.py tests/functional: enable debug logging for QEMUMachine 2024-11-25 10:13:33 +00:00
tuxruntest.py tests/functional: remove obsolete reference to avocado bug 2024-11-25 10:06:20 +00:00
utils.py tests/functional: Convert BananaPi tests to the functional framework 2024-11-04 14:16:12 +01:00