[checkbox-ce-oem] Modify dbus warm cold boot job (BugFix)#1038
[checkbox-ce-oem] Modify dbus warm cold boot job (BugFix)#1038rickwu666666 merged 11 commits intocanonical:mainfrom
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1038 +/- ##
==========================================
- Coverage 44.10% 40.52% -3.58%
==========================================
Files 358 335 -23
Lines 38765 37365 -1400
Branches 6571 6348 -223
==========================================
- Hits 17096 15143 -1953
- Misses 21006 21585 +579
+ Partials 663 637 -26
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
kissiel
left a comment
There was a problem hiding this comment.
Race condition with the background process scheduling found.
...rib/checkbox-provider-ce-oem/units/strict-confinement/powermanagement-strict-confinement.pxu
Outdated
Show resolved
Hide resolved
@rickwu666666 , I think you can reference this PR |
9324e7c to
017f551
Compare
|
I've pushed a fix for the race condition. |
stanley31huang
left a comment
There was a problem hiding this comment.
In test plan, we are going to compare the logs between the reboot test, so we need to add a job to collect logs before reboot test.
017f551 to
e9bb247
Compare
|
@stanley31huang , Yes you are correct. I've pushed the fix. Thanks for the review. |
kissiel
left a comment
There was a problem hiding this comment.
Going through an extra snap seems unnecessary. It:
- obfuscates what is being done
- reduces clarity and makes the whole thing less readable and debuggable
- creates unnecessary dependencies
Also there's a serious race condition with Checkbox being created here that may lead to breakage of other jobs that may follow the one modified here.
...rib/checkbox-provider-ce-oem/units/strict-confinement/powermanagement-strict-confinement.pxu
Outdated
Show resolved
Hide resolved
...rib/checkbox-provider-ce-oem/units/strict-confinement/powermanagement-strict-confinement.pxu
Outdated
Show resolved
Hide resolved
e9bb247 to
d3e2ae4
Compare
d3e2ae4 to
72eeb9f
Compare
|
@stanley31huang, |
|
I think we should have some extra steps to reboot the system in case we failed to power control the system via |
Since we change the command name in test-strict-confinement snap. Fix the wrong job name in test-plan
Make the job easier to read
Due to -m on is for debugging purpose
Since we need initial status of the system
Change calling dbus logic to prevent auto job hang
72eeb9f to
caa1c57
Compare
|
https://certification.canonical.com/hardware/202403-33886/submission/386662/test-results/fail/ |
Since we change the command name in the test-strict-confinement snap.
Make the job easier to read
Description
We modify the command in the test-strict-confinement snap. Therefore, we modify the command that is called in the job.
Also, fix the wrong job ID that is included in the test plan.
Resolved issues
N/A
Documentation
N/A
Tests
Warm-boot
https://certification.canonical.com/hardware/202304-31485/submission/359313/
Cold-boot
https://certification.canonical.com/hardware/202304-31485/submission/359311/