Unable to select those automatically skipped jobs

Bug #1368001 reported by Po-Hsu Lin
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Checkbox Converged
Fix Released
Medium
Maciej Kisielewski
Checkbox GUI (Legacy)
Won't Fix
Medium
Unassigned
Next Generation Checkbox (CLI)
Fix Released
Medium
Maciej Kisielewski
PlainBox (Toolkit)
Won't Fix
Medium
Maciej Kisielewski

Bug Description

If a job is skipped automatically, you will be unable to select them for re-run.

How to reproduce:
1. Select the SD card insert, storage and remove job
2. Wait for the insert job to time-out
3. Try to re-run them

Even the insert one passed after re-run, you are still unable to re-run the storage and remove job.

Related branches

Gavin Lin (gavin.lin)
tags: added: ce-qa-concern
Revision history for this message
Gavin Lin (gavin.lin) wrote :

This also affect oem qa, but not urgent request.

Changed in checkbox-gui:
milestone: none → 0.28
importance: Undecided → High
milestone: 0.28 → 0.29
Changed in checkbox-gui:
importance: High → Medium
Chris Gregan (cgregan)
Changed in checkbox-gui:
status: New → Confirmed
Revision history for this message
Chris Gregan (cgregan) wrote :

We need to look into whether the UI is aware of what cases are dependencies for a skipped case.
Solution would be changing the function of the automated skipped test's re-run button to bulk reset all the dependent tests to re-run.

Changed in checkbox-gui:
milestone: 0.29 → 0.30
Changed in checkbox-gui:
milestone: 0.30 → future
Po-Hsu Lin (cypressyew)
Changed in checkbox-ng:
status: New → Confirmed
Revision history for this message
Pierre Equoy (pieq) wrote :

Issue lp:1449837 might be related to this as well.

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

The old GUI won't be fixed. The CLI and checkbox-touch should.

Changed in checkbox-gui:
status: Confirmed → Won't Fix
milestone: future → none
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

The re-run code should be handled by SessionAssistant so that the behavior is consistent across applications.

Changed in plainbox:
status: New → Confirmed
assignee: nobody → Maciej Kisielewski (kissiel)
Changed in checkbox-ng:
assignee: nobody → Maciej Kisielewski (kissiel)
Changed in checkbox-touch:
assignee: nobody → Maciej Kisielewski (kissiel)
status: New → Confirmed
Changed in checkbox-converged:
importance: Undecided → Medium
Changed in checkbox-ng:
importance: Undecided → Medium
Changed in checkbox-converged:
status: Confirmed → In Progress
Changed in checkbox-ng:
status: Confirmed → In Progress
Changed in plainbox:
status: Confirmed → In Progress
importance: Undecided → Medium
Revision history for this message
Maciej Kisielewski (kissiel) wrote :

Marking as 'won't fix' for plainbox, as it doesn't support rerunning.

Changed in plainbox:
status: In Progress → Won't Fix
Changed in checkbox-converged:
status: In Progress → Fix Committed
Changed in checkbox-ng:
status: In Progress → Fix Committed
Changed in checkbox-converged:
milestone: none → 1.2.3
Changed in checkbox-ng:
milestone: none → 0.23
milestone: 0.23 → 0.22
Pierre Equoy (pieq)
Changed in checkbox-ng:
status: Fix Committed → Fix Released
Changed in checkbox-converged:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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