dependency engine has no way of showing the traceback for Panic() failures
Bug #1722810 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
| 2.2 |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
Currently when a Catacomb runs a worker, it traps the panic() stack trace (which we then assert in the test suite). However the final error you get in log files is just:
worker exited unexpectedly: panic ...
It would be much easier for us to debug what is going on if we had a way to display the original panic stack trace (which we are already saving in memory).
| Changed in juju: | |
| status: | Triaged → In Progress |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| milestone: | 2.3.0 → 2.3-beta2 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/
is the patch against 2.2