hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3975) test-patch can report the modifications found in the workspace along with the error message
Date Tue, 26 Aug 2008 01:21:44 GMT

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

Hadoop QA commented on HADOOP-3975:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 688923.

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

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

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3098/console

This message is automatically generated.

> 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: build
>            Reporter: Hemanth Yamijala
>            Priority: Minor
>         Attachments: 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.

View raw message