Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1363337689.1248284234881.JavaMail.jira@brutus>
Date: Wed, 22 Jul 2009 10:37:14 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6164) Test-patch's method of checking for
 new tests is not correct
In-Reply-To: <1144829364.1248220514920.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HADOOP-6164:
------------------------------------------------

> BTW hudson didnt run any core-test for HDFS-450
Why it is related to BTW HDFS-450?  Typo?

I think Jakob was talking about [this test results|https://issues.apache.org/jira/browse/HDFS-458?focusedCommentId=12732863&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12732863].  It got +1 on contrib test.

Giridharan, could you take a second look?

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