PlainBox (Toolkit)

most clients use single-session API

Bug #1312731 reported by Rod Smith
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Checkbox GUI (Legacy)
Won't Fix
Undecided
Unassigned
Next Generation Checkbox (CLI)
Fix Released
Undecided
Zygmunt Krynicki
Next Generation Checkbox (CLI) 0.4
PlainBox (Toolkit)
Fix Released
Undecided
Zygmunt Krynicki
PlainBox (Toolkit) 0.6

Bug Description

During a run of canonical-certification-server, temporary log files are stored in ~/.cache/plainbox/sessions and elsewhere; however, these files are deleted upon successful termination of the run. ("Successful" being defined to include runs with failures of individual tests.) In some cases, though, getting access to these log files is desirable. For instance, bug #1304436 is proving resistant to reproduction by running isolated tests. Thus, an option to leave the temporary files in place is desirable. In fact, it might be worth considering setting that as the default, and to delete the temporary files only if another run is initiated.

Revision history for this message
Michael F. Miller (mikem1355) wrote :

I have also been affected by this issue. Rather than deleting the various logs they should be stored in one central location and preserved.

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

PlainBox has multi-session API (ability to have many sessions and not remove the last one over and over) but almost no clients actually use it. This is also complicated by checkbox-gui/dbus using the single-session API and having some hard baked things based on that design (so it's possible but more costly to change that).

In addition, before we really use multi-session API for everything we should add a tool (plainbox subcommand?) that could list and remove sessions that we don't need anymore.

Changed in plainbox:
status: New → Confirmed
summary: - canonical-certification-server deletes temporary files
+ most clients use single-session API
Changed in checkbox-gui:
status: New → Confirmed
Changed in checkbox-ng:
status: New → Confirmed
Revision history for this message
Rod Smith (rodsmith) wrote :

Bug 1304436 was recently marked as a duplicate of this one. If they've really got the same underlying cause, then the importance of addressing this cause is rather high, because it's creating extra work in the form of a need to run the test suite multiple times. This isn't just internal to Canonical, either; our partners are running into this problem (in the form of the symptoms reported in bug 1304436).

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

In trunk (and the dev ppa), plainbox run is alredy multi-session. checkbox-ng is still to follow (so server certification commands are not muli-session yet). In addition the resume logic is far better and handles errors gracefully so we should never implicitly remove sessions in such cases.

Changed in plainbox:
status: Confirmed → In Progress
Changed in checkbox-ng:
status: Confirmed → In Progress
assignee: nobody → Zygmunt Krynicki (zkrynicki)
Changed in plainbox:
assignee: nobody → Zygmunt Krynicki (zkrynicki)
status: In Progress → Fix Committed
milestone: none → 0.6
Changed in checkbox-ng:
milestone: none → 0.4
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I'm marking this as fix-committed in checkbox-ng since with --new-ui (which will become default today) we are no longer using the single session API

Changed in checkbox-ng:
status: In Progress → Fix Committed
Sylvain Pineau (sylvain-pineau)
Changed in checkbox-ng:
status: Fix Committed → Fix Released
Changed in plainbox:
status: Fix Committed → Fix Released
Sylvain Pineau (sylvain-pineau)
Changed in checkbox-gui:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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