aboutsummaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc/kdoc_parser.py
diff options
context:
space:
mode:
authorDaniel P. Berrangé <berrange@redhat.com>2025-09-08 14:57:21 +0100
committerThomas Huth <thuth@redhat.com>2025-09-09 15:45:26 +0200
commit2ee187dcb55aee7f70b514db772090649235de70 (patch)
treecd5c0531caeb0bd6151bdb874f4ae75b2fc3b7dc /scripts/lib/kdoc/kdoc_parser.py
parente5381b041037f3918163f2b7f82415aee80cd64e (diff)
downloadqemu-2ee187dcb55aee7f70b514db772090649235de70.zip
qemu-2ee187dcb55aee7f70b514db772090649235de70.tar.gz
qemu-2ee187dcb55aee7f70b514db772090649235de70.tar.bz2
tests/functional: avoid tearDown failure when QEMU dies
In a QEMU process under test dies unexpectedly, the 'shutdown' method may well raise an exception. This causes the tearDown method to fail, which means any later cleanup code fails to get run. Most notably the log handlers don't get removed so the base.log file from an earlier test will get polluted with messages from any subsequent tests. The tearDown failure also results in pages of exceptions printed on the console, which obscures the real failure message / trace printed by the test. Ignore any shutdown failures in the tearDown method, since any test which cares about clean shutdown should have already cleaned up any running VMs. The tearDown method is just there as a safety net to cleanup resources. The base.log file will still containing log messages from the failed 'vm.shutdown' call too. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com> Message-ID: <20250908135722.3375580-4-berrange@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions