Autopilot's ProcessSearchError stack trace is unhelpful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
High
|
Unassigned | ||
autopilot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This traceback:
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
**kwargs
File "/usr/lib/
dbus_bus
File "/usr/lib/
dbus_
File "/usr/lib/
process
File "/usr/lib/
% return_code
ProcessSearchError: Process exited with exit code: -5
Needs to be improved. If it exits with a signal (-ve RC), we should print both the numeric, and string values of that signal. We should also print which process this is talking about, and the PID of the exited process.
Related branches
- Christopher Lee (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 196 lines (+126/-9)3 files modifiedautopilot/introspection/__init__.py (+67/-6)
autopilot/tests/functional/test_ap_apps.py (+8/-2)
autopilot/tests/unit/test_exceptions.py (+51/-1)
Changed in autopilot: | |
milestone: | none → 1.4 |
status: | Fix Committed → Fix Released |
Changed in autopilot (Ubuntu): | |
status: | New → Fix Released |
Changed in autopilot (Ubuntu Saucy): | |
status: | New → Fix Released |
Fix committed into lp:autopilot/1.3 at revision 348, scheduled for release in autopilot, milestone Unknown