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 "Nigel Daley (JIRA)" <ji...@apache.org> on 2009/01/23 02:57:59 UTC
[jira] Commented: (HADOOP-5112) Upgrade Clover to 2.4.2 and enable
Test Optimization in HADOOP
[ https://issues.apache.org/jira/browse/HADOOP-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666388#action_12666388 ]
Nigel Daley commented on HADOOP-5112:
-------------------------------------
Thanks Nick. I believe this is likely a duplicate of HADOOP-3921, which has been fixed. I'm currently getting the build working on a new Hudson slave. Once its working, I think we'll see Clover 2.3.2 results. Then we can upgrade the jar to 2.4.2 provided Apache's license for Clover covers that.
> Upgrade Clover to 2.4.2 and enable Test Optimization in HADOOP
> --------------------------------------------------------------
>
> Key: HADOOP-5112
> URL: https://issues.apache.org/jira/browse/HADOOP-5112
> Project: Hadoop Core
> Issue Type: Task
> Components: build
> Reporter: Nick Pellow
>
> The current [Hadoop build|http://hudson.zones.apache.org/hudson/view/Hadoop/job/Hadoop-trunk/clover/] on Hudson is using Clover 1.3.13.
> I will attach a patch to the build.xml and the clover 2.4.2 jar to this issue.
> Test Optimization works by only running tests for which code has changed. This can be used both in a CI environment and on a developers machine to make running tests faster.
> Clover will also run tests which previously failed. Modified source code is detected at compile time and then used to select the tests that get run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.