[
https://issues.apache.org/jira/browse/HADOOP-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734543#action_12734543
]
Giridharan Kesavan commented on HADOOP-6164:
--------------------------------------------
I agree with you and I would follow up with this issue.
But this is for the first time I'm hearing something like this.
If you agree that this not something to do with test-patch then I can openup a
different jira and deal with hudson issue or we can file a bug with hudson dev.
thanks
> 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.
