Hi,
we have a similar error for Directory builds, but we use Cobertura:
FATAL: Unable to parse
/home/hudson/hudson/jobs/dir-shared-metrics/builds/2010-10-19_06-00-39/coverage.xml
hudson.util.IOException2: Cannot parse coverage results
at
hudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:89)
at
hudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:52)
at
hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:262)
...
Caused by: org.xml.sax.SAXParseException: XML document structures must
start and end within the same entity.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
...
Kind Regards,
Stefan
[1]
https://hudson.apache.org/hudson/view/Directory/job/dir-shared-metrics/34/console
On Tue, Oct 19, 2010 at 9:37 AM, Uwe Schindler <u...@thetaphi.de> wrote:
>> -----Original Message-----
>> From: Niklas Gustavsson [mailto:nik...@protocol7.com]
>> Sent: Tuesday, October 19, 2010 9:22 AM
>> To: builds@apache.org
>> Subject: Re: Hudson Master's Clover parsing broken?
>>
>> On Tue, Oct 19, 2010 at 8:27 AM, Uwe Schindler <u...@thetaphi.de> wrote:
>> > Since yesterday morning the clover xml parsing is again sometimes
>> > broken on master. Is this maybe an issue when transferring the file
>> > from the slave to master?
>>
>> I've tried to restart slaves without any success. I'm wondering if this
> might be a
>> incompatibility between the Clover plugin and the new Hudson remoting
> code. I
>> would recommend checking with the Hudson devs if this is a known issue.
>
> The strange thing is that this only happens sometimes. We run the clover
> builds since days and sometimes they fail only about half of the time. Also
> the plugin works for other builds with exactly the same configuration
> without any problems.
>
> I downloaded failed clover.xml from the workspace, which looks fine and
> parses sucessfully. I will ask about this on hudson's dev list.
>
> Uwe
>
>
