fwts changes to the desktop certification whitelist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Daniel Manrique |
Bug Description
For 14.04, we will need these changes to the fwts test in desktop certification
(These changes are only for desktop, so, please, don't modify the default fwts test, we will just remove this one from the whitelists and create a new one).
1) Remove the fwts_test from the desktop whitelists
2) Create a new job called "firmware/
- acpidump
- version
- acpitables
- apicinstance
- hpet_check
- mcfg
- method
- mpcheck
- msr
- mtrr
- apicedge
- klog
3) Create a new job (under cpu) called cpu/cstates that runs the fwts cstates test. Fail on HIGH or CRITICAL as usual. Attach the log as usual. Add it to the whitelists.
4) Remove the S3,S4 checklog test from the whitelist, but keep attaching the S3/S4 logs
5) Create a new job called miscellanea/oops that runs the fwts oops test. Fail on HIGH or CRITICAL as usual. Attach the log as usual. Add it to the whitelists.
6) Create a new job called firmware/wakealarm that runs the fwts wakealarm test. Fail on HIGH or CRITICAL as usual. Attach the log as usual. Add it to the whitelists.
7) Create a new job called firmware/
Related branches
- Brendan Donegan (community): Approve
- Daniel Manrique (community): Needs Resubmitting
-
Diff: 227 lines (+86/-14)5 files modifiedproviders/plainbox-provider-certification-client/whitelists/client-cert.whitelist (+13/-7)
providers/plainbox-provider-certification-client/whitelists/client-selftest.whitelist (+13/-7)
providers/plainbox-provider-checkbox/jobs/cpu.txt.in (+20/-0)
providers/plainbox-provider-checkbox/jobs/firmware.txt.in (+20/-0)
providers/plainbox-provider-checkbox/jobs/miscellanea.txt.in (+20/-0)
no longer affects: | checkbox |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
milestone: | none → 0.7 |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
Hi,
Can I change the test names?
We already have a local job that builds sub-tests for all fwts-supported tests, so items 3 and 5 would be simply additions to the whitelist, with no new test writing required. Actually, items 6 and 7 were implemented this way.
The difference vs. what was requested here is that the tests will be called firmware/cstates and firmware/oops, instead of cpu/cstates and miscellanea/oops.
I'll submit the MR with exactly what was requested here but leave it pending confirmation of whether it's OK to change the test names a bit.