Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 28 Nov 2016 05:55:58 +0000 (UTC)
From: "Akira Ajisaka (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12991863.1469202368000.375009.1480312558479@Atlassian.JIRA>
In-Reply-To: <JIRA.12991863.1469202368000@Atlassian.JIRA>
References: <JIRA.12991863.1469202368000@Atlassian.JIRA> <JIRA.12991863.1469202368629@arcas>
Subject: [jira] [Commented] (MAPREDUCE-6743) nativetask unit tests need to
 provide usable output; fix link errors during mvn test
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 28 Nov 2016 05:56:00 -0000


    [ https://issues.apache.org/jira/browse/MAPREDUCE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701016#comment-15701016 ] 

Akira Ajisaka commented on MAPREDUCE-6743:
------------------------------------------

Sorry for being very late.
Mostly looks good to me. I have one question: What version (or hashtag?) of the gtest in this patch? I'm thinking adding this information to the release note or description makes it easier for tracking if there is something to do.

> nativetask unit tests need to provide usable output; fix link errors during mvn test
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6743
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6743
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: nativetask
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: MAPREDUCE-5743.00.patch, MAPREDUCE-5743.01.patch, MAPREDUCE-5743.02.patch, MAPREDUCE-5743.03.patch
>
>
> Currently, hadoop-mapreduce-client-nativetask creates a nttest binary which provides an binary exit code to determine failure.  This means there is no output generated by the Jenkins run to actually debug or provide hints as to what failed.  Given that nttest is written with gtest, it should be configured to either spit out junit or TAP which can then be used to provide further analysis.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org