Interrupted runs are recovered even if the user selects "No" when prompted
Bug #836623 reported by
Daniel Manrique
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
High
|
Brendan Donegan | ||
checkbox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Tested with Checkbox trunk on Oneiric and with 0.11.3 on Natty.
Steps to reproduce:
- run checkbox-gtk
- On the test selection screen, deselect all tests and mark just a few categories.
- Start the test run.
- When on the first test screen, close checkbox.
- Start checkbox-gtk again.
- When prompted to recover the incomplete test run, select "No".
Expected behavior:
- Selection screen reset to its initial state.
Actual behavior:
- Old run data remains, including prior test selection.
The usual workaround is to delete the checkbox data directory, either $HOME/.checkbox or $HOME/.
Related branches
lp:~brendan-donegan/checkbox/fix_rerun
- Marc Tardif (community): Approve
-
Diff: 47 lines (+8/-1)3 files modifieddebian/changelog (+1/-0)
plugins/jobs_prompt.py (+5/-1)
plugins/recover_prompt.py (+2/-0)
lp:~roadmr/ubuntu/oneiric/checkbox/0.12.7
- Daniel Holbach (community): Needs Information
-
Diff: 8336 lines (+2048/-1194)32 files modifiedcheckbox/job.py (+9/-0)
checkbox/lib/transport.py (+26/-1)
checkbox/parsers/udev.py (+16/-4)
checkbox/report.py (+39/-12)
checkbox/tests/report.py (+1/-1)
checkbox/variables.py (+1/-1)
checkbox_gtk/gtk_interface.py (+6/-5)
checkbox_gtk/hyper_text_view.py (+3/-1)
data/whitelists/default.whitelist (+1/-0)
debian/changelog (+27/-0)
debian/control (+2/-2)
debian/po/it.po (+17/-9)
jobs/disk.txt.in (+1/-1)
jobs/info.txt.in (+9/-0)
jobs/mediacard.txt.in (+1/-1)
jobs/memory.txt.in (+2/-2)
jobs/monitor.txt.in (+1/-1)
jobs/suspend.txt.in (+2/-2)
plugins/intro_prompt.py (+2/-4)
plugins/jobs_prompt.py (+5/-0)
plugins/launchpad_prompt.py (+2/-2)
plugins/launchpad_report.py (+25/-18)
plugins/recover_prompt.py (+1/-2)
plugins/report_prompt.py (+7/-0)
plugins/suites_prompt.py (+2/-3)
po/es.po (+91/-92)
po/hu.po (+230/-209)
po/it.po (+588/-363)
po/zh_CN.po (+250/-233)
po/zh_TW.po (+147/-224)
report/hardware-1_0.rng (+533/-0)
scripts/gconf_resource (+1/-1)
Changed in checkbox (Ubuntu): | |
status: | New → Confirmed |
Changed in checkbox: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Canonical Hardware Certification (canonical-hw-cert) |
milestone: | none → 0.12.5 |
milestone: | 0.12.5 → 0.12.6 |
Changed in checkbox: | |
status: | Triaged → In Progress |
Changed in checkbox: | |
status: | In Progress → Fix Committed |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The only fundamental difference between Yes and No seems to be that Yes brings you directly to the last test run whereas No does show the test selection screen and then returns to the last run test (I can only guess what happens if you deselected the saved test from the list)