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

Ramya R commented on HADOOP-3975:
---------------------------------

Ran test-patch locally, here are the results:
 [exec] +1 overall.

     [exec]     +1 @author.  The patch does not contain any @author tags.

     [exec]     +1 tests included.  The patch appears to include 3 new or 
modified tests.

     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.

     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.

     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.



> test-patch can report the modifications found in the workspace along with the 
> error message
> -------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3975
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3975
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: test
>            Reporter: Hemanth Yamijala
>            Assignee: Ramya R
>            Priority: Minor
>             Fix For: 0.19.0
>
>         Attachments: hadoop-3975-v1.txt, Hadoop-3975-v2.txt, hadoop-3975.txt, 
> test-patch1.txt
>
>
> When test-patch is run on a developer workspace which contains modifications, 
> it errors out by saying "ERROR: can't run in a workspace that contains 
> modifications". It appears this is printed when svn stat command returns a 
> non-empty output. It would be helpful to report this output, so that 
> developers can be alerted to what modifications are causing this error. 
> Sometimes these modifications may not be because of a direct code change 
> they've done, but remnants of an incorrect cleanup of the last build, etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to