diff options
| author | John Snow <jsnow@redhat.com> | 2022-01-31 23:11:32 -0500 |
|---|---|---|
| committer | John Snow <jsnow@redhat.com> | 2022-02-02 14:12:22 -0500 |
| commit | 50465f94d211beabfbfc80e4f85ec4fad0757570 (patch) | |
| tree | bf8655489b2aa82dc78a029a44b0d6e534c1db73 /python/setup.py | |
| parent | fa73e6e4ca1a93c5bbf9d05fb2a25736ab810b35 (diff) | |
| download | focaccia-qemu-50465f94d211beabfbfc80e4f85ec4fad0757570.tar.gz focaccia-qemu-50465f94d211beabfbfc80e4f85ec4fad0757570.zip | |
python/machine: raise VMLaunchFailure exception from launch()
This allows us to pack in some extra information about the failure, which guarantees that if the caller did not *intentionally* cause a failure (by capturing this Exception), some pretty good clues will be printed at the bottom of the traceback information. This will help make failures in the event of a non-negative return code more obvious when they go unhandled; the current behavior in _post_shutdown() is to print a warning message only in the event of signal-based terminations (for negative return codes). (Note: In Python, catching BaseException instead of Exception catches a broader array of Exception events, including SystemExit and KeyboardInterrupt. We do not want to "wrap" such exceptions as a VMLaunchFailure, because that will 'downgrade' the exception from a BaseException to a regular Exception. We do, however, want to perform cleanup in either case, so catch on the broadest scope and wrap-and-re-raise only in the more targeted scope.) Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Hanna Reitz <hreitz@redhat.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Message-id: 20220201041134.1237016-3-jsnow@redhat.com Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'python/setup.py')
0 files changed, 0 insertions, 0 deletions