aboutsummaryrefslogtreecommitdiff
path: root/scripts/qapi
diff options
context:
space:
mode:
authorFabiano Rosas <farosas@suse.de>2024-01-04 11:21:43 -0300
committerPeter Xu <peterx@redhat.com>2024-01-16 11:16:09 +0800
commite33b6712dba206547a313a6f2608b0fd967ee558 (patch)
tree22b62fbaf58e7578f68713cb96bd5c305d16b597 /scripts/qapi
parent679a7382a389875c0f7835a1a409ebf4859f8410 (diff)
downloadqemu-e33b6712dba206547a313a6f2608b0fd967ee558.zip
qemu-e33b6712dba206547a313a6f2608b0fd967ee558.tar.gz
qemu-e33b6712dba206547a313a6f2608b0fd967ee558.tar.bz2
tests/qtest/migration: Add a wrapper to print test names
Our usage of gtest results in us losing the very basic functionality of "knowing which test failed". The issue is that gtest only prints test names ("paths" in gtest parlance) once the test has finished, but we use asserts in the tests and crash gtest itself before it can print anything. We also use a final abort when the result of g_test_run is not 0. Depending on how the test failed/broke we can see the function that trigged the abort, which may be representative of the test, but it could also just be some generic function. We have been relying on the primitive method of looking at the name of the previous successful test and then looking at the code to figure out which test should have come next. Add a wrapper to the test registration that does the job of printing the test name before running. Signed-off-by: Fabiano Rosas <farosas@suse.de> Reviewed-by: Peter Xu <peterx@redhat.com> Link: https://lore.kernel.org/r/20240104142144.9680-7-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com>
Diffstat (limited to 'scripts/qapi')
0 files changed, 0 insertions, 0 deletions