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 548A0200BE4 for ; Wed, 21 Dec 2016 19:45:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4EB37160B26; Wed, 21 Dec 2016 18:45:46 +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 910DF160B18 for ; Wed, 21 Dec 2016 19:45:45 +0100 (CET) Received: (qmail 46282 invoked by uid 500); 21 Dec 2016 18:45:44 -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 46269 invoked by uid 99); 21 Dec 2016 18:45:44 -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; Wed, 21 Dec 2016 18:45:44 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0FB3EDFC15; Wed, 21 Dec 2016 18:45:44 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1846: CLOUDSTACK-9688: Fix failing smoke tests Content-Type: text/plain Message-Id: <20161221184544.0FB3EDFC15@git1-us-west.apache.org> Date: Wed, 21 Dec 2016 18:45:44 +0000 (UTC) archived-at: Wed, 21 Dec 2016 18:45:46 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1846 Thanks @serg38 Merging this on discretion, and manual test results. The previous failing tests on test_templates and test_list_ids pass now. --- 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. ---