[
https://issues.apache.org/jira/browse/MAPREDUCE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478331#comment-15478331
]
Allen Wittenauer commented on MAPREDUCE-6743:
---------------------------------------------
Digging into this further, it's pretty clear that the cmakebuilder plug-in is
capturing the info we want, but doing it in the most proprietary way possible.
It might be possible to modify it, but I think that's going well beyond the
scope. Instead, I think I'll do the following:
take -01 then modify the pom settings a bit more so that we write
TEST-nativetask-nttest.xml from gtest and
nativetask-nttest.pstatus/stderr/stdout from cmakebuilder to surefire-reports.
Then if we ever fix cmakebuilder to use the correct names/write junit/xunit
xml, it'll be ready to go. Doing this also makes Jenkins and Yetus pick up the
xml file and makes it slightly easier to find the output.
> nativetask unit tests need to provide usable output
> ---------------------------------------------------
>
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
