Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0AF6118E55 for ; Wed, 2 Dec 2015 21:07:13 +0000 (UTC) Received: (qmail 64112 invoked by uid 500); 2 Dec 2015 21:07:11 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 63878 invoked by uid 500); 2 Dec 2015 21:07:11 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 63047 invoked by uid 99); 2 Dec 2015 21:07:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2015 21:07:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 29D052C1F7A for ; Wed, 2 Dec 2015 21:07:11 +0000 (UTC) Date: Wed, 2 Dec 2015 21:07:11 +0000 (UTC) From: "Bob Hansen (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-9448) Enable valgrind for libhdfspp unit tests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036624#comment-15036624 ] Bob Hansen commented on HDFS-9448: ---------------------------------- I would very much like [~aw]'s feedback (at least at a high level). There are three knobs that can be turned here: * Setting the skip.valgrind.tests for mvn * Passing in an explicit set of flags through maven to cmake * If valgrind is not found by cmakes's find_program (which can be passed a hint where to find it using the valgrind_dir cmake property) If any of the three indicate that we should not run valgrind tests, they are not added to the test suite. The default is to run the hdfspp unit tests (not integration tests) both with and without valgrind. Does that seem idiomatically in line with the rest of the Hadoop build infrastructure? We can open a separate issue to add valgrind to the yetus image. [~aw] - Should that be an HDFS Jira or a Yetus Jira? > Enable valgrind for libhdfspp unit tests > ---------------------------------------- > > Key: HDFS-9448 > URL: https://issues.apache.org/jira/browse/HDFS-9448 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs-client > Reporter: Bob Hansen > Assignee: Bob Hansen > Attachments: HDFS-9448.HDFS-8707.000.patch, HDFS-9448.HDFS-8707.001.patch, HDFS-9448.HDFS-8707.002.patch > > > We should have a target that runs the unit tests under valgrind if it is available on the target machine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)