environs tests not well isolated
Bug #1154942 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
If you do:
cd juju-core/environs
go test -gocheck.v -gocheck.f Default
You'll get a panic about
"cannot share a state between two dummy environs; old "only"; new "erewhemos"
However, if you run all tests, then everything passes. Apparently one of the Default tests isn't cleaning up after itself, and some *other* test is cleaning things up by the time the TestNewFromName
Related branches
lp://staging/~axwalk/juju-core/lp1154942-fix-environs-test-teardown
- Juju Engineering: Pending requested
-
Diff: 23 lines (+5/-1)1 file modifiedenvirons/config_test.go (+5/-1)
| Changed in juju-core: | |
| status: | Confirmed → Triaged |
| tags: | added: bitesize |
| Changed in juju-core: | |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| milestone: | none → dev-docs |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | dev-docs → none |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | none → 1.14.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
