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

Hadoop QA commented on HADOOP-8562:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12567057/branch-trunk-win.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 32 new 
or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 2017 javac 
compiler warnings (more than the trunk's current 2014 warnings).

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 1.3.9) warnings.

        {color:red}-1 release audit{color}.  The applied patch generated 4 
release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-assemblies hadoop-common-project/hadoop-common hadoop-dist 
hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle
 hadoop-tools/hadoop-streaming hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests:

                  org.apache.hadoop.fs.TestFileUtil
                  
org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager
                  
org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerShutdown
                  
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch
                  
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2117//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2117//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2117//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-common.html
Javac warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2117//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2117//console

This message is automatically generated.
                
> Enhancements to Hadoop for Windows Server and Windows Azure development and 
> runtime environments
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8562
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8562
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 3.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: branch-trunk-win.patch, branch-trunk-win.patch, 
> branch-trunk-win.patch, branch-trunk-win.patch, branch-trunk-win.patch, 
> branch-trunk-win.patch, branch-trunk-win.patch, test-untar.tar, test-untar.tgz
>
>
> This JIRA tracks the work that needs to be done on trunk to enable Hadoop to 
> run on Windows Server and Azure environments. This incorporates porting 
> relevant work from the similar effort on branch 1 tracked via HADOOP-8079.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to