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 9FEB72009FB for ; Fri, 6 May 2016 18:05:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9E8B2160A0C; Fri, 6 May 2016 16:05:47 +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 DE94E1608F8 for ; Fri, 6 May 2016 18:05:46 +0200 (CEST) Received: (qmail 84596 invoked by uid 500); 6 May 2016 16:05:46 -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 84585 invoked by uid 99); 6 May 2016 16:05:45 -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; Fri, 06 May 2016 16:05:45 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 66635DFC7E; Fri, 6 May 2016 16:05:45 +0000 (UTC) From: dmabry To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CPU socket count reporting correction Content-Type: text/plain Message-Id: <20160506160545.66635DFC7E@git1-us-west.apache.org> Date: Fri, 6 May 2016 16:05:45 +0000 (UTC) archived-at: Fri, 06 May 2016 16:05:47 -0000 Github user dmabry commented on the pull request: https://github.com/apache/cloudstack/pull/1520#issuecomment-217485432 We have rolled this patch in our lab and verified that it does indeed report the number of sockets correctly. Based on testing this LGTM. Please do a force push to kick off jenkins and travis again. --- 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. ---