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 1B092200C22 for ; Tue, 21 Feb 2017 23:14:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1988A160B68; Tue, 21 Feb 2017 22:14:28 +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 59550160B4F for ; Tue, 21 Feb 2017 23:14:27 +0100 (CET) Received: (qmail 84992 invoked by uid 500); 21 Feb 2017 22:14:26 -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 84966 invoked by uid 99); 21 Feb 2017 22:14:26 -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, 21 Feb 2017 22:14:26 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 199BBDFADC; Tue, 21 Feb 2017 22:14:26 +0000 (UTC) From: dmabry To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c... Content-Type: text/plain Message-Id: <20170221221426.199BBDFADC@git1-us-west.apache.org> Date: Tue, 21 Feb 2017 22:14:26 +0000 (UTC) archived-at: Tue, 21 Feb 2017 22:14:28 -0000 Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1915 @serbaut Can you do a force push to kick off jenkins again. I'm guessing Jenkins just had an issue and not the PR. --- 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. ---