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 9423B200B92 for ; Wed, 28 Sep 2016 19:01:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 92C2F160AD3; Wed, 28 Sep 2016 17:01:29 +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 CE9EE160AB8 for ; Wed, 28 Sep 2016 19:01:28 +0200 (CEST) Received: (qmail 37472 invoked by uid 500); 28 Sep 2016 17:01:27 -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 37457 invoked by uid 99); 28 Sep 2016 17:01:27 -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, 28 Sep 2016 17:01:27 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 89C55E03CE; Wed, 28 Sep 2016 17:01:27 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping... Content-Type: text/plain Message-Id: <20160928170127.89C55E03CE@git1-us-west.apache.org> Date: Wed, 28 Sep 2016 17:01:27 +0000 (UTC) archived-at: Wed, 28 Sep 2016 17:01:29 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1692 I'm investigating failures on this PR, likely most of them (esp related to oobm) are env related as udp traffic seems to be blocked. There also seems to be an error with the log upload script where file incorrectly gets uploaded resulting in few byte sized zip files (I've fixed it as well). --- 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. ---