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 "Giridharan Kesavan (JIRA)" <ji...@apache.org> on 2009/07/22 08:12:14 UTC

[jira] Resolved: (HADOOP-6164) Test-patch's method of checking for new tests is not correct

     [ https://issues.apache.org/jira/browse/HADOOP-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Giridharan Kesavan resolved HADOOP-6164.
----------------------------------------

    Resolution: Invalid
      Assignee: Giridharan Kesavan

Im closing this resolved invalid.
This is how hudson works and this has nothing to do with the test-patch script.

> Test-patch's method of checking for new tests is not correct
> ------------------------------------------------------------
>
>                 Key: HADOOP-6164
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6164
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>            Reporter: Jakob Homan
>            Assignee: Giridharan Kesavan
>
> As happened in HDFS-458, test-patch/hudson saw the previous patch(HDFS-492) add a new test, bringing the total number of tests to 49.  Then it tested 458, which had no new tests as it was a change to the build file.  492 had not yet been committed yet, so there were still only 48 tests in trunk.  But test-patch failed the patch, expecting 49 tests.  test-patch should check the correct number of tests based on trunk, not on whatever number it last saw.

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