Open richtja opened 3 weeks ago
Attention: Patch coverage is 26.66667%
with 11 lines
in your changes missing coverage. Please review.
Project coverage is 54.44%. Comparing base (
6b55d5a
) to head (7420e5f
). Report is 4 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
avocado/plugins/vmimage.py | 14.28% | 6 Missing :warning: |
avocado/utils/vmimage.py | 37.50% | 5 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Hi @richtja ,
Thanks for working on this. While this gets the most important thing done, that is, info about a failure, IMO a
--debug
option should:1. Also work during success cases, that is, it should show what's going on whether the operation is succeeding or failing 2. Should not crash the application
Have you tried adding various logging entries to the
avocado.utils.vmimage
module and making them visible when--debug
is given?
Hi @clebergnu, thanks for your review. I have changed this PR to use logging instead of raising errors. Please have a look.
This commit adds a new option to
vmimage get
feature calleddebug
. It brings possibility to run vmimage command in debug mode to get more detailed information about possible failures. In debug mode, all exceptions caused by vmimage utility will be raised to console. That should provide enough information for further debugging of possible issues.Reference: #6051
vmimage get
without debug:vmimage get
with debug: