hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8584) test-patch.sh should not immediately exit when no tests are added or modified
Date Tue, 10 Jul 2012 19:38:35 GMT

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

Colin Patrick McCabe commented on HADOOP-8584:
----------------------------------------------

bq. Btw, was this change made to demand that all patches, unless doc or log changes, be provided
with a patch?

No.  It seems to have been an unintented issue introduced by the patch for HADOOP-8523.
                
> test-patch.sh should not immediately exit when no tests are added or modified
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-8584
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8584
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>
> test-patch.sh should not immediately exit when no tests are added or modified.
> Although it's good to note whether or not a patch introduces or modifies tests, it's
not good to abort the Jenkins patch process if it did not.

--
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

        

Mime
View raw message