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 6C879200BD5 for ; Thu, 24 Nov 2016 07:00:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6B055160B0A; Thu, 24 Nov 2016 06:00:06 +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 AD367160AFD for ; Thu, 24 Nov 2016 07:00:05 +0100 (CET) Received: (qmail 66240 invoked by uid 500); 24 Nov 2016 05:59:59 -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 66223 invoked by uid 99); 24 Nov 2016 05:59:59 -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, 24 Nov 2016 05:59:59 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4E0BDDFCC8; Thu, 24 Nov 2016 05:59:59 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1766: CLOUDSTACK-9598: wrong defaut gateway for the nic in... Content-Type: text/plain Message-Id: <20161124055959.4E0BDDFCC8@git1-us-west.apache.org> Date: Thu, 24 Nov 2016 05:59:59 +0000 (UTC) archived-at: Thu, 24 Nov 2016 06:00:06 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1766 @murali-reddy lgtm, can you see why the same test passed again given no change to the PR was made? Do you think this new test could become a source of intermittent failure? --- 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. ---