Bootstrap job for zapper-enabled test plan (New)#1352
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1352 +/- ##
==========================================
+ Coverage 44.18% 44.20% +0.02%
==========================================
Files 359 359
Lines 38813 38827 +14
Branches 6581 6585 +4
==========================================
+ Hits 17148 17162 +14
+ Misses 21003 21002 -1
- Partials 662 663 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@rmartin013, we'll need to properly configure your setups with |
Hook25
left a comment
There was a problem hiding this comment.
This LGTM, if the api PR is approved, please do (re-)test this and merge it
If not feel free to link it
|
Tested on the same environment as the linked issue. Running latest beta: FAILED, see https://certification.canonical.com/hardware/202210-30711/submission/382542/test-results/?term=resolution_before_suspend Running this branch: |
* Add: zapper reset bootstrap job * Fix: removed deprecated zapper-enabled job
Description
When a device is hooked up with a Zapper, depending on the previous conditions of the setup, its presence might affect the other test cases, like seen in https://github.com/canonical/checkbox/issues/1326.
This PR introduces a new bootstrap job, to clear Zapper-related environment before running the actual test plan.
It assumes that the Zapper setup is correctly configured, via
zapper setup, since it will unplug USB sticks if not configured for provisioning.Resolved issues
Resolves CHECKBOX-1481 and https://github.com/canonical/checkbox/issues/1326.
Documentation
N/A
Tests
See #1352 (comment).