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

Hudson commented on HADOOP-8523:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2446 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2446/])
    HADOOP-8523. test-patch.sh doesn't validate patches before building (Jack 
Dintruff via jeagles) (Revision 1358394)

     Result = FAILURE
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1358394
Files : 
* /hadoop/common/trunk/dev-support/smart-apply-patch.sh
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt

                
> test-patch.sh doesn't validate patches before building
> ------------------------------------------------------
>
>                 Key: HADOOP-8523
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8523
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.23.3, 2.0.1-alpha
>            Reporter: Jack Dintruff
>            Priority: Minor
>              Labels: newbie
>             Fix For: 2.0.1-alpha, 3.0.0
>
>         Attachments: HADOOP-8523.patch, HADOOP-8523.patch, Hadoop-8523.patch, 
> Hadoop-8523.patch
>
>
> When running test-patch.sh with an invalid patch (not formatted properly) or 
> one that doesn't compile, the script spends a lot of time building Hadoop 
> before checking to see if the patch is invalid.  It would help devs if it 
> checked first just in case we run test-patch.sh with a bad patch file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to