The manifest should be the requirement of a generated job instead of the generator's requirement (Thunderbolt)

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

Bug Description

For the Thunderbolt audio test generator, the manifest should be the requirement of its generated job, instead of the requirement of the generator.

Thing is, if you start checkbox on a freshly install system, if the generator job has the manifest requirement, it will be skipped before the test case selection section, because the manifest entry wasn't generated yet.

Work flow of the manifest collector:

1. Select whitelist
2. Job generation stage, it run through all generators
3. Job selection section
4. Test started, manifest will be collected here, ideally it will be collected before all other test cases.

As you can see here, things will go wrong on step 2 with manifest requirement for generators

Related branches

Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → In Progress
Changed in plainbox-provider-canonical-certification:
milestone: none → 0.17
importance: Undecided → Medium
Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
status: In Progress → Fix Committed
Changed in plainbox-provider-canonical-certification:
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.