Autopilot should log when it patches an environment variable
Bug #1236097 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 | ||
Saucy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Autopilot should log something when it patches an environment variable. Currently we log when we reset the variable, but not when we patch it. This can make it hard to debug problems that occur only when inside a test (due to a different environment being loaded).
Related branches
lp:~thomir-deactivatedaccount/autopilot/1.3-fix-patch-environment
- PS Jenkins bot: Approve (continuous-integration)
- Christopher Lee (community): Approve
-
Diff: 27 lines (+10/-0)1 file modifiedautopilot/testcase.py (+10/-0)
lp:~thomir-deactivatedaccount/autopilot/trunk-fix-patch-environment
- PS Jenkins bot: Approve (continuous-integration)
- Christopher Lee (community): Approve
-
Diff: 27 lines (+10/-0)1 file modifiedautopilot/testcase.py (+10/-0)
Changed in autopilot: | |
status: | Fix Committed → Fix Released |
milestone: | none → 1.4 |
To post a comment you must log in.
Fix committed into lp:autopilot/1.3 at revision 345, scheduled for release in autopilot, milestone Unknown