You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Ramya R (JIRA)" <ji...@apache.org> on 2008/09/12 12:09:44 UTC

[jira] Created: (HADOOP-4165) test-patch script is showing questionable number of Javac warnings

test-patch script is showing questionable number of Javac warnings
------------------------------------------------------------------

                 Key: HADOOP-4165
                 URL: https://issues.apache.org/jira/browse/HADOOP-4165
             Project: Hadoop Core
          Issue Type: Test
          Components: test
    Affects Versions: 0.18.0
            Reporter: Ramya R
            Priority: Minor
             Fix For: 0.19.0


test-patch is recording 881 number of javac warnings when run on trunk and 216 javac warnings when run on "ANY" patch.
This behavior was observed even on an empty patch.

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

[jira] Updated: (HADOOP-4165) test-patch script is showing questionable number of Javac warnings

Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nigel Daley updated HADOOP-4165:
--------------------------------

    Fix Version/s:     (was: 0.19.0)
                   0.20.0

Not a blocker for 0.19

> test-patch script is showing questionable number of Javac warnings
> ------------------------------------------------------------------
>
>                 Key: HADOOP-4165
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4165
>             Project: Hadoop Core
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.18.0
>            Reporter: Ramya R
>            Priority: Minor
>             Fix For: 0.20.0
>
>
> test-patch is recording 881 number of javac warnings when run on trunk and 216 javac warnings when run on "ANY" patch.
> This behavior was observed even on an empty patch.

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