Need a job firmware/fwts_desktop_diagnosis_hwe

[Jerry Kao]

Alex@HWE proposed to separate fwts logs into 2 parts, one is results_oem.log for OEM and the other is results_hwe.log for HWE.
Their expectation is that, if the failures are related to OEM and in results_oem.log, QA file bug and asing to PM directly, no need HWE's analysis. And once the failures need HWE's analysis (in results_hwe.log), QA file bug and assign to engineering TL.

In new release plainbox-provider-checkbox, we have a new test firmware/fwts_desktop_diagnosis_results_hwe.log to collect fwts logs for hwe analysis. But when test firmware/fwts_desktop_diagnosis fail, QA has no idea what part is fail (maybe both) and who should the bug assign to?

I think we need two separate jobs/tests for fwts test. When test(s) fail, QA can clearly know who should the bug(s) assign to.

Test to Run in FWTS and identify which test results need HWE to analysis
https://wiki.canonical.com/PES/Engineering/HardwareEnablement/FWTS/TestSuggestions#Tests_to_Run

[Po-Hsu Lin (cypressyew)]

Call it a wishlist since it looks like a feature request.

[Po-Hsu Lin (cypressyew)]

Switch to "High" as Jerry suggested.