The azure provider test TestDestroyControllerErrors sometimes fails as the order of the errors checked is the reverse of the expected. Perhaps the test shouldn't really care which error is listed first?
<http://reports.vapour.ws/releases/issue/576accd4749a562da5cd856b>
FAIL: environ_test.go:917: environSuite.TestDestroyControllerErrors
[LOG] 0:00.001 DEBUG juju.provider.azure opening model "testenv"
[LOG] 0:00.001 DEBUG juju.provider.azure destroying model "testenv"
[LOG] 0:00.001 DEBUG juju.provider.azure - deleting resource groups
[LOG] 0:00.002 DEBUG juju.provider.azure - deleting resource group "group1"
[LOG] 0:00.002 DEBUG juju.provider.azure - deleting resource group "group2"
environ_test.go:960:
c.Assert(destroyErr, gc.ErrorMatches,
`deleting resource group "group1":.* failed with `+firstErr+`; `+
`deleting resource group "group2":.* failed with `+secondErr)
... error string = "deleting resource group \"group1\": deleting resource group \"group1\": autorest:DoErrorUnlessStatusCode DELETE https://api.azurestack.local/subscriptions/22222222-2222-2222-2222-222222222222/resourcegroups/group1?api-version=2014-04-01-preview failed with foo; deleting resource group \"group2\": deleting resource group \"group2\": autorest:DoErrorUnlessStatusCode DELETE https://api.azurestack.local/subscriptions/22222222-2222-2222-2222-222222222222/resourcegroups/group2?api-version=2014-04-01-preview failed with bar"
... regex string = "deleting resource group \"group1\":.* failed with bar; deleting resource group \"group2\":.* failed with foo"
http:// reviews. vapour. ws/r/5170/