[
https://issues.apache.org/jira/browse/HADOOP-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-3921:
------------------------------
Attachment: hadoop-3921.patch
When we had the problem before we were using Clover 1. This patch updates the
build to use Clover 2, which has some differences to do with how the ant task
is defined: http://confluence.atlassian.com/display/CLOVER/1.+QuickStart+Guide.
You now need to specify a {{clover.home}} property for ant.
I tested with Clover 2.3.2 which is the version on Hudson, and it managed to
instrument all the source (which is where it failed before), and run a test. I
had to increase the memory available to ant to perform the instrumentation (see
http://confluence.atlassian.com/pages/viewpage.action?pageId=79986966), using
{code}
export ANT_OPTS=-Xmx256m
{code}
I think we could try enabling this on Hudson again to see if it works.
> Clover breaks nightly builds
> ----------------------------
>
> Key: HADOOP-3921
> URL: https://issues.apache.org/jira/browse/HADOOP-3921
> Project: Hadoop Core
> Issue Type: Bug
> Components: build
> Reporter: Tom White
> Attachments: hadoop-3921.patch
>
>
> Since 8 July the nightly builds on Hudson have failed with the following
> error:
> [clover] Processing files at 1.3 source level.
> [clover] Updating database at
> '/zonestorage/hudson/home/hudson/hudson/jobs/Hadoop-trunk/workspace/trunk/build/test/clover/db/hadoop_coverage.db'
> [clover]
> /var/tmp/clover35762.tmp/src35763.tmp/org/apache/hadoop/fs/FileUtil.java.tmp:508:10:unexpected
> token: OSType
> [clover] line 508: unexpected token: OSType
> [clover] ** Error(s) occurred and the instrumentation process can't
> continue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
