Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9941C200B6D for ; Tue, 23 Aug 2016 10:58:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 97C89160AAD; Tue, 23 Aug 2016 08:58:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DE36C160AA5 for ; Tue, 23 Aug 2016 10:58:07 +0200 (CEST) Received: (qmail 47505 invoked by uid 500); 23 Aug 2016 08:58:07 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 47484 invoked by uid 99); 23 Aug 2016 08:58:06 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2016 08:58:06 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 9F8D2E0230; Tue, 23 Aug 2016 08:58:06 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request #1648: test/integration: fix tearDown order in list_... Content-Type: text/plain Message-Id: <20160823085806.9F8D2E0230@git1-us-west.apache.org> Date: Tue, 23 Aug 2016 08:58:06 +0000 (UTC) archived-at: Tue, 23 Aug 2016 08:58:08 -0000 GitHub user rhtyd reopened a pull request: https://github.com/apache/cloudstack/pull/1648 test/integration: fix tearDown order in list_acl_ tests test/integration: fix tearDown order in list_acl_ tests In several of the list_acl_tests, the tests run for simulator only where in the (class) setup domains and accounts are created for the test. When the tests end the (class) teardown methods would delete and remove these resources. Due to dependence of one of the resources on the other, domain2 on domain1, domain2 needs to be removed/cleaned up before domain1. Due to this issue, several Travis test runs have failed in the past such as: https://travis-ci.org/apache/cloudstack/jobs/152610967 https://travis-ci.org/apache/cloudstack/jobs/152610968 Changing the order of cleanup fixes the tests. /cc @jburwell @karuturi The fix is specific to tests that run 'only' on simulator with Travis. A passing Travis run should be enough to validate the changes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.9-fixmarvintest Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1648.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1648 ---- commit a9acadda95c05a6af1f7c1ebf1dd2591479fd8ba Author: Rohit Yadav Date: 2016-08-19T11:42:09Z test/integration: fix tearDown order in list_acl_ tests In several of the list_acl_tests, the tests run for simulator only where in the (class) setup domains and accounts are created for the test. When the tests end the (class) teardown methods would delete and remove these resources. Due to dependence of one of the resources on the other, domain2 on domain1, domain2 needs to be removed/cleaned up before domain1. Due to this issue, several Travis test runs have failed in the past such as: https://travis-ci.org/apache/cloudstack/jobs/152610967 https://travis-ci.org/apache/cloudstack/jobs/152610968 Changing the order of cleanup fixes the tests. Signed-off-by: Rohit Yadav ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---