Skipped TestUniterUpgradeConflicts on ppc64
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Low
|
Unassigned | ||
Bug Description
TestUniterUpgra
<http://
FAIL: uniter_test.go:874: com_juju_
...
[LOG] 0:02.965 INFO juju.worker.
[LOG] 0:02.965 INFO juju.worker.
[LOG] 0:02.965 INFO juju.worker.
[LOG] 0:02.966 DEBUG juju.worker.uniter [AGENT-STATUS] idle
[LOG] 0:02.966 DEBUG juju.apiserver <- [C8] unit-u-0 {"RequestId"
[LOG] 0:02.971 DEBUG juju.apiserver -> [C8] unit-u-0 4.765ms {"RequestId"
want resolved mode "", got "no-hooks"; still waiting
...
want resolved mode "", got "no-hooks"; still waiting
[LOG] 0:05.390 INFO juju.mongo dialled mongo successfully on address "[::1]:60357"
want resolved mode "", got "no-hooks"; still waiting
...
want resolved mode "", got "no-hooks"; still waiting
util_test.go:722:
c.Fatalf("never reached desired status")
... Error: never reached desired status
[LOG] 0:12.970 INFO juju.worker.uniter ModeAbide exiting
The uniter tests have long been somewhat flakey in the ppc test run, but this one may well just be broken since the leadership landing.
| Eric Snow (ericsnowcurrently) wrote : | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |


http:// reviews. vapour. ws/r/1488/