Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27E0E181B2 for ; Thu, 10 Dec 2015 13:01:18 +0000 (UTC) Received: (qmail 17740 invoked by uid 500); 10 Dec 2015 13:01:17 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 17684 invoked by uid 500); 10 Dec 2015 13:01:17 -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 17668 invoked by uid 99); 10 Dec 2015 13:01:17 -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; Thu, 10 Dec 2015 13:01:17 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4B169E1782; Thu, 10 Dec 2015 13:01:17 +0000 (UTC) From: wilderrodrigues To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: [4.7] CLOUDSTACK-9129: list vpc routers b... Content-Type: text/plain Message-Id: <20151210130117.4B169E1782@git1-us-west.apache.org> Date: Thu, 10 Dec 2015 13:01:17 +0000 (UTC) Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1197#issuecomment-163604337 That's odd! :( Same test was executed by @remibergsma and I this week and everything went fine. But if that was rebased, the test should now be under ```smoke``` instead of ```component```. Although it would not change anything in the test itself. @remibergsma: could you please put one of you 8 bubble to run the test_network_ops.py ? You have your one-liner! ;) The MCT-Shared has also changed. The run tests script is getting the tests from smoke instead of component. Cheers, Wilder --- 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. ---