hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gary murry (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6164) Test-patch's method of checking for new tests is not correct
Date Thu, 23 Jul 2009 21:49:14 GMT

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

gary murry commented on HADOOP-6164:
------------------------------------

Hi Giri,

If another jira is being opened for this, can we make sure an link the issues for tracking?
 I think it is agreed that this is not a test-patch issue, but rather a hudson issue.

Thanks,
-Gary

> 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.


Mime
View raw message