Autopilot Eventually matcher gives an obscure message inside the Eventually matcher
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Committed
|
High
|
Unassigned | ||
autopilot (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The Eventually matcher calls into the DBus interface. If the DBus backend died, we print a stack trace, instead of raising a custom exception. The stack trace is:
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
mismatch = matcher.
File "/usr/lib/
wait_
File "/usr/lib/
_, new_state = self.parent.
File "/usr/lib/
return self.get_
File "/usr/lib/
return cls._Backend.
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
We should catch this and raise a better exception instead.
Related branches
- Christopher Lee (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 141 lines (+83/-6)3 files modifiedautopilot/introspection/backends.py (+20/-5)
autopilot/tests/functional/test_dbus_query.py (+17/-0)
autopilot/tests/unit/test_introspection_backends.py (+46/-1)
Changed in autopilot: | |
importance: | Critical → High |
Changed in autopilot: | |
assignee: | Thomi Richards (thomir) → nobody |
Fix committed into lp:autopilot at revision 558, scheduled for release in autopilot, milestone 1.4