Comment 1 for bug 1306468

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.