From 6401683e0beacbbc8c89a7356c169618d11b4fc0 Mon Sep 17 00:00:00 2001 From: Matt Clay Date: Wed, 20 Mar 2019 22:22:23 -0700 Subject: [PATCH] Mark azure_rm_hdinsightcluster test unstable. The unstable alias wasn't intended for slow but otherwise stable tests. However, the alternatives are to either dedicate an entire test group to this one test or mark it unsupported. Marking it unstable at least permits the test to run when changes are made to the integration test or the module itself, which is better than not running the tests at all. --- test/integration/targets/azure_rm_hdinsightcluster/aliases | 1 + 1 file changed, 1 insertion(+) diff --git a/test/integration/targets/azure_rm_hdinsightcluster/aliases b/test/integration/targets/azure_rm_hdinsightcluster/aliases index 095e5ec347..4fda2983d0 100644 --- a/test/integration/targets/azure_rm_hdinsightcluster/aliases +++ b/test/integration/targets/azure_rm_hdinsightcluster/aliases @@ -1,3 +1,4 @@ cloud/azure destructive shippable/azure/group1 +unstable # test is slow (~30 minute run time), not unstable, but this is better than unsupported