Enable support for lttng tracing in autopilot
Bug #1177612 reported by
Thomi Richards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Autopilot |
Fix Released
|
Critical
|
Unassigned | ||
| autopilot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
We need to be able to support lttng tracing in autopilot. This means:
* emitting a test-started and test-stopped trace event at the beginning and end of every test case that's run.
* Adding options to 'autopilot run' to start lttng tracing at the start of the autopilot run, and stop it at the end.
Related branches
lp:~thomir-deactivatedaccount/autopilot/add_lttng_tracepoint_emit
- PS Jenkins bot: Approve (continuous-integration)
- Christopher Lee (community): Approve
-
Diff: 232 lines (+134/-2)7 files modifiedautopilot/testcase.py (+20/-0)
debian/control (+13/-0)
debian/python-autopilot-trace.install (+1/-0)
debian/rules (+3/-0)
lttng_module/autopilot_tracepoint.c (+52/-0)
lttng_module/autopilot_tracepoint.h (+37/-0)
setup.py (+8/-2)
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #1 |
| Changed in autopilot: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in autopilot (Ubuntu): | |
| status: | New → Fix Released |
| Changed in autopilot: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #3 |
| Changed in autopilot (Ubuntu Raring): | |
| status: | New → Won't Fix |
To post a comment you must log in.
Fix committed into lp:autopilot at revision 203, scheduled for release in autopilot, milestone 1.3.1