unit-test failure MachineSuite.TestManageModelRunsInstancePoller

[John George]

Unit-test failure as seen here:
http://reports.vapour.ws/releases/issue/56bd8634749a56369e8d01fa

[John A Meinel (jameinel)]

Seen again here:
http://ci.jujucharms.com/job/github-merge-juju/374/testReport/junit/github/com_juju_juju_cmd_jujud_agent/TestPackage/

[LOG] 0:10.065 DEBUG juju.worker.dependency "http-server" manifold worker stopped: listen tcp :44120: bind: address already in use
[LOG] 0:10.065 ERROR juju.worker.dependency "http-server" manifold worker returned unexpected error: listen tcp :44120: bind: address already in use
[LOG] 0:10.065 DEBUG juju.worker.dependency stack trace:
listen tcp :44120: bind: address already in use
github.com/juju/juju/worker/httpserver/worker.go:107:
[LOG] 0:10.065 DEBUG juju.worker.dependency "raft-transport" manifold worker stopped: <nil>
[LOG] 0:10.065 DEBUG juju.worker.dependency "api-server" manifold worker stopped: <nil>
[LOG] 0:10.075 DEBUG juju.worker.dependency "raft-transport" manifold worker stopped: "http-server" not running: dependency not available
[LOG] 0:10.126 DEBUG juju.worker.dependency "api-server" manifold worker stopped: "http-server" not running: dependency not available
machine_test.go:274:
    m, instId := s.waitProvisioned(c, unit)
machine_test.go:326:
    c.Fatalf("timed out waiting for provisioning")
... Error: timed out waiting for provisioning

[John A Meinel (jameinel)]

Though maybe the actual failure is just ye-old "address already in use" and it just happens to be expressed in this particular test this particular time.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]