plainbox puts too many jobs in a session, causing spurious resume failures
Bug #1378300 reported by
Jonathan Cave
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Fix Released
|
Critical
|
Zygmunt Krynicki |
Bug Description
Version: 0.14+bzr3326+
On trying to resume a session (imported from another user), I was presented with following error:
$ plainbox run -i 2014.com.
=======
There is 1 incomplete session that might be resumed
Do you want to resume session 'pbox-my25w8u6'?
r => resume this session
n => next session
c => create new session
[rnc]: r
Definition of job '2013.com.
This session cannot be resumed
Pick an action
i => ignore this problem
e => erase this session
[ie]:
Related branches
lp:~zyga/checkbox/fix-1378300
- Daniel Manrique (community): Approve
-
Diff: 467 lines (+264/-14)8 files modifiedplainbox/plainbox/abc.py (+14/-0)
plainbox/plainbox/impl/result.py (+14/-0)
plainbox/plainbox/impl/session/jobs.py (+2/-3)
plainbox/plainbox/impl/session/resume.py (+46/-4)
plainbox/plainbox/impl/session/suspend.py (+69/-1)
plainbox/plainbox/impl/session/test_resume.py (+23/-6)
plainbox/plainbox/impl/session/test_suspend.py (+92/-0)
plainbox/plainbox/impl/test_result.py (+4/-0)
Changed in plainbox: | |
status: | In Progress → Fix Committed |
milestone: | none → 0.14 |
Changed in plainbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This error happens when the user has two providers, say A and B. The user starts a test session with a few jobs from the B provider selected. Meanwhile the session is stopped and the A provider gets updated. After that the user won't be able to resume the session even though that none of the jobs in B were changed.