The new fwts_test script will break the firmware/fwts_$1.log attachment job

Bug #1487953 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
Fix Released
Low
Sylvain Pineau
Provider for Plainbox - Canonical Certification (Legacy)
Fix Released
Medium
Po-Hsu Lin

Bug Description

We have a pair of fwts tests in our job definition file, the "firmware/fwts_$1", which will be generated by the "firmware/fwts" local job, and its attachment job "firmware/fwts_$1.log", which will be generated by the "firmware/fwts_logs" local job
These two jobs will be generated base on the fwts_test --list output.

However, with the recent change in fwts, the following test cases will have a trailing "_hwe" in the filename
HWE_TESTS = ['mtrr',
             'virt',
             'apicedge',
             'klog',
             'oops',
             'uefibootpath']

This filename change will cause the attachment jobs fail.

Affected test plans (with both firmware/fwts and firmware/fwts_logs in the test plan):
certification-client:
client-cert-14-04.pxu
client-cert-14-04-3.pxu
client-cert.whitelist
client-selftest.whitelist
client-selftest-14-04.whitelist

CDTS:
ihv-firmware.pxu
ihv-firmware-advanced.pxu

(certification-server provider was not affected)

But luckily,
it seems that only the CDTS provider do have the separated test cases for fwts, therefore this bug do have some impact on it.
For the test plans in certification-client provider, they just run the local job, so I think we can safely remove them.

Related branches

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

BTW, I think we should rename this kind of local jobs, maybe rename them with a "generator-" prefix, so that it will become easier to read in the test plan, also, we could run all the local jobs by just running "generator-.* job".

Changed in plainbox-provider-checkbox:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Po-Hsu Lin (cypressyew)
Changed in cdts:
importance: Undecided → High
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in plainbox-provider-checkbox:
assignee: Po-Hsu Lin (cypressyew) → Sylvain Pineau (sylvain-pineau)
Changed in cdts:
assignee: nobody → Sylvain Pineau (sylvain-pineau)
Changed in plainbox-provider-canonical-certification:
assignee: nobody → Sylvain Pineau (sylvain-pineau)
Changed in cdts:
status: New → In Progress
Changed in plainbox-provider-canonical-certification:
status: New → In Progress
importance: Undecided → Medium
Changed in plainbox-provider-checkbox:
status: In Progress → Fix Committed
Changed in cdts:
status: In Progress → Invalid
status: Invalid → Fix Committed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With the fix landed on checkbox, CDTS still affected by this issue,
as those tests in ihv-firmware.pxu will run the test with "-t" for fwts, therefore "_hwe" will exist in the file name.
e.g. firmware/fwts_oops test will run:
fwts_test -t oops -l $PLAINBOX_SESSION_SHARE/fwts_oops.log

Changed in cdts:
status: Fix Committed → Confirmed
Changed in plainbox-provider-canonical-certification:
assignee: Sylvain Pineau (sylvain-pineau) → Po-Hsu Lin (cypressyew)
status: In Progress → Fix Committed
Revision history for this message
Sylvain Pineau (sylvain-pineau) wrote :

CDTS is a bit special as the official release are offline tarballs. But the tests using -t won't generate the hwe logs so even the local job creating the jobs for cdts with -t will benefit from the fix.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Ahh, ok, it's "without -t", I misread this section, thanks!
We're good now.

Changed in cdts:
status: Confirmed → Fix Committed
Changed in plainbox-provider-checkbox:
milestone: none → 0.22
Changed in cdts:
milestone: none → 1.12
Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
milestone: none → 0.19
Changed in plainbox-provider-checkbox:
status: Fix Committed → Fix Released
Changed in plainbox-provider-canonical-certification:
status: Fix Committed → Fix Released
Changed in cdts:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.