Bug #1485908 “Post suspend test sync: camera tests” : Bugs : Provider for Plainbox - Canonical Certification (Legacy)

Post suspend test sync: camera tests

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

Bug Description

We need to add the post-suspend version for the following camera tests:
camera/detect
camera/still
camera/display
camera/multiple-resolution-images

Related branches

Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → In Progress
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

From the CDTS provider, I noticed that we already have:
    camera/display_after_suspend
    camera/still_after_suspend
    camera/multiple_resolution_after_suspend
in the suspend.txt.in of the checkbox provider.

Another question is that do we need the camera/detect job to be re-tested?
If we don't, we just need to patch the certification-client provider.

* Note that if we try to use suspend/display_after_suspend instead of camera/display_after_suspend for the motion capture job, its name will collide with the after suspend graphic display job, so it good to leave it as-is.

Changed in plainbox-provider-canonical-certification:
status: In Progress → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

<PHLin> ara, hello, one question to the post-suspend camera test
<PHLin> ara, we have four camera tests: detect, still, display, multiple-res
<PHLin> ara, do we need the detect test after suspend? or just the rest of three will be fine?
<ara> PHLin, I think the rest should be enough. Actually, I think just still and display should be enough
<PHLin> ara, ok, I will just add these two
<PHLin> ara, CDTS already have these three post-suspend tests, I will leave it there
<ara> PHLin, sounds good
<PHLin> ara, oh btw, these should be blockers no matter in which test plan, right?
<ara> PHLin, yes
<PHLin> ara, okok

So the CDTS provider needs a fix for the blocker status.

Po-Hsu Lin (cypressyew)
Changed in cdts:
assignee: nobody → Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
status: Incomplete → In Progress
Changed in cdts:
status: New → In Progress
importance: Undecided → High
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in plainbox-provider-canonical-certification:
status: In Progress → Fix Committed
Daniel Manrique (roadmr)
Changed in cdts:
status: In Progress → Fix Committed
Po-Hsu Lin (cypressyew)
Changed in cdts:
milestone: none → 1.12
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

The patch for certification-client provider is not complete, please refer to the following MR for patches in all other test plans:
https://code.launchpad.net/~cypressyew/plainbox-provider-canonical-certification/+git/plainbox-provider-canonical-certification/+merge/268566/+index?ss=1

Po-Hsu Lin (cypressyew)
Changed in plainbox-provider-canonical-certification:
milestone: none → 0.19
Changed in plainbox-provider-canonical-certification:
status: Fix Committed → Fix Released
Po-Hsu Lin (cypressyew)
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

Loading subscribers...

Remote bug watches

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