Merge ~bettyl/plainbox-provider-checkbox:add-after-suspend-manual-thunderbolt-thumderbolt3-tests into plainbox-provider-checkbox:master
Status: | Merged |
---|---|
Approved by: | Jonathan Cave |
Approved revision: | 015a9a7cd030f438923253c6d1e176fb41f0e627 |
Merged at revision: | 8b02e63676ab10521cd258c2b24463bd36a1a698 |
Proposed branch: | ~bettyl/plainbox-provider-checkbox:add-after-suspend-manual-thunderbolt-thumderbolt3-tests |
Merge into: | plainbox-provider-checkbox:master |
Diff against target: |
124 lines (+63/-0) 2 files modified
units/thunderbolt/jobs.pxu (+30/-0) units/thunderbolt/test-plan.pxu (+33/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Cave (community) | Approve | ||
Betty Lin (community) | Needs Resubmitting | ||
Review via email: mp+368638@code.launchpad.net |
Description of the change
I have tested this in a stock Ubuntu 18.04 with adding "after-
When I do:
$ checkbox-cli list-bootstrapped com.canonical.
The thunderbolt/
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
Although this will probably work as you have shown in your testing, I think it might be sensible not to rely on the after-suspend flags in this case.
The depends fields in the jobs are trying to ensure the jobs are run in a series with the storage-test and remove jobs depending on the insert job.
For example after-suspend- manual- thunderbolt/ storage- test should have a depends field identifying after-suspend- manual- thunderbolt/ insert. I think I might consider using a "sibling" job in this case.
The test plan modifications are fine.