provider/oracle test stipple
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
John A Meinel | ||
2.3 |
Fix Released
|
Medium
|
John A Meinel |
Bug Description
I don't know if this is a sign of a bug we are ignoring, or a sign that we're logging to something other than the logging infrastructure, but we shouldn't be seeing this while running a test suite that passes cleanly:
=== RUN TestPackage
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
2018-02-16 08:20:27 WARNING juju.provider.
OK: 83 passed
--- PASS: TestPackage (1.19s)
PASS
ok github.
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Well, there are two things here.
One is that the base test suite isn't using one of the ones that includes the logging suite, and secondly, it does look like some instances aren't being deleted.