db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: Emma report generation fails
Date Mon, 16 Apr 2012 10:13:08 GMT
siddharth srivastava <akssps011@gmail.com> writes:

> Hi
> I have been trying to generate code coverage report(suites.All) with
> Emma. I was
> able to instrument the jar files and run the test cases. But the report
> generation fails with the following error:
> java.io.UTFDataFormatException: malformed input around byte 52
>         at java.io.DataInputStream.readUTF(Unknown Source)
>         at java.io.DataInputStream.readUTF(Unknown Source)
>         at com.vladium.emma.data.ClassDescriptor.readExternal(ClassDescriptor.ja
> va:171)
>         at com.vladium.emma.data.MetaData.readExternal(MetaData.java:228)
>         at com.vladium.emma.data.DataFactory.readEntry(DataFactory.java:770)
>         at com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:461)
>         at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
>         at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:175
> )
>         at com.vladium.emma.Processor.run(Processor.java:54)
>         at com.vladium.emma.report.reportCommand.run(reportCommand.java:130)
>         at emma.main(emma.java:40)
> I see that Knut also faced this error earlier,
> http://permalink.gmane.org/gmane.comp.apache.db.derby.devel/93262
> Has there been a workaround for this ?

I haven't investigated it further, but it still happens every other day
(on average) in a nightly job I have running in my environment.

I suspect that it is caused by one of the tests that spawn new Java
processes, and that the spawned processes write coverage data
concurrently and somehow end up corrupting the file for each other if
the timing is right.

Knut Anders

View raw message