-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: adding extra scenarios for fault injection #14489
tests: adding extra scenarios for fault injection #14489
Conversation
This change includes some scenarios that are missing to check fault injection. In this case are included fault/reboot for: - install snapd --dangerous - remodel - install kernel component - update boot config
65bd947
to
426b153
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
One more idea about possible scenarios is a transaction updating both the base snap and snapd. Depending on how far has the installation process advanced a failure should either roll back the complete thing, or finish updating both snaps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a comment on what is the expected outcome of the tests
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #14489 +/- ##
==========================================
+ Coverage 78.83% 78.87% +0.03%
==========================================
Files 1078 1080 +2
Lines 145096 145826 +730
==========================================
+ Hits 114389 115017 +628
- Misses 23546 23617 +71
- Partials 7161 7192 +31
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although I have a question
#TAG/gadget_panic_config_bootloader: update-config-bootloader | ||
#FAULT/gadget_panic_config_bootloader: panic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the one that finishes with error? Maybe worth adding a comment on why it is commented out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is an scenario that cannot be reproduced, I'll work on that one in a following pr, I need @valentindavid for that
This change includes some scenarios that are missing to check fault injection.
In this case are included fault/reboot for: