TestWaitSSHRefreshAddresses can fail on windows

[Martin Packman]

The CI windows unit test run sometimes hits a failure on TestWaitSSHRefreshAddresses where it's expecting 0.1.2.4 but gets 0.1.2.3 instead.

<http://reports.vapour.ws/releases/issue/559ca56f749a5659ed091eba>
<http://reports.vapour.ws/releases/4155/job/run-unit-tests-win2012-amd64/attempt/2613>

----------------------------------------------------------------------
FAIL: bootstrap_test.go:350: BootstrapSuite.TestWaitSSHRefreshAddresses

[LOG] 0:00.124 DEBUG juju.provider.common connection attempt for 0.1.2.3 failed: mock connection failure to 0.1.2.3
bootstrap_test.go:369:
    c.Check(stderr, gc.Matches,
        "Waiting for address\n"+
            "(.|\n)*(Attempting to connect to 0.1.2.4:22\n)+(.|\n)*")
... value string = "" +
... "Waiting for address\n" +
... "Attempting to connect to 0.1.2.3:22\n"
... regex string = "" +
... "Waiting for address\n" +
... "(.|\n" +
... ")*(Attempting to connect to 0.1.2.4:22\n" +
... ")+(.|\n" +
... ")*"

WARNING: Error cleaning up temporaries: remove c:\users\admini~1\appdata\local\temp\tmpunubjh\gogo\tmp-juju-testopn4pk\check-2696223601554009790\9\provider-state: The process cannot access the file because it is being used by another process.OOPS: 42 passed, 1 FAILED
--- FAIL: TestPackage (2.54s)
FAIL
FAIL github.com/juju/juju/provider/common 2.870s

[Mick Gregg (macgreagoir)]

I can reproduce by adjusting the timeout, so looks like a reliance on the clock.

[Curtis Hovey (sinzui)]

This test is skipped on windows. It has not been seen in testing since 2016-02-09

[Tim Penhey (thumper)]

Only ubuntu is supported as a controller OS, so don't run these tests on other OS.