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

Hudson commented on HADOOP-11639:
---------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2096 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2096/])
HADOOP-11639. Clean up Windows native code compilation warnings related to 
Windows Secure Container Executor. Contributed by Remus Rusanu. (cnauroth: rev 
3836ad6c0b3331cf60286d134157c13985908230)
* 
hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/yarn/server/nodemanager/windows_secure_container_executor.c
* hadoop-common-project/hadoop-common/src/main/winutils/task.c
* hadoop-common-project/hadoop-common/src/main/winutils/client.c
* hadoop-common-project/hadoop-common/src/main/winutils/include/winutils.h
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-common/src/main/winutils/systeminfo.c
* hadoop-common-project/hadoop-common/src/main/winutils/libwinutils.c
* hadoop-common-project/hadoop-common/src/main/winutils/service.c
* hadoop-common-project/hadoop-common/src/main/winutils/config.cpp


> Clean up Windows native code compilation warnings related to Windows Secure 
> Container Executor.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11639
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11639
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: native
>    Affects Versions: 2.6.0
>            Reporter: Chris Nauroth
>            Assignee: Remus Rusanu
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11639.00.patch, HADOOP-11639.01.patch, 
> HADOOP-11639.02.patch, HADOOP-11639.03.patch
>
>
> YARN-2198 introduced additional code in Hadoop Common to support the 
> NodeManager {{WindowsSecureContainerExecutor}}.  The patch introduced new 
> compilation warnings that we need to investigate and resolve.



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

Reply via email to