-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using cobertura 2.0.3 fails with no coverage - fails in saveCoverageData #88
Comments
I also see ERROR messages for saveCoverageData, loadCoverageData; however in my case Cobertura successfully creates the coverage report. Unlike above case, I don't get a SEVERE message with exception. Not sure whether to open a new issue for my scenario - after all, report generation works fine, so it's more of me wondering why i see errors when everything appears to succeed. Setup: Maven 3.0.4, Java 1.7, Cobertura Maven plugin 2.6, cobertura 2.0.3. Invoked with: Output (sanitized): [INFO] >>> cobertura-maven-plugin:2.6:cobertura (default) @ myProject >>> [ERROR] Oct 30, 2013 1:34:15 PM net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler saveCoverageData [INFO] pom.xml contains:
|
Still no luck, more logs here. [ERROR] Oct 30, 2013 5:28:55 PM net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler loadCoverageData Error: Unable to read from data file /x/workspace/jenkinsjob/projects/domain/domain-project/target/cobertura/cobertura.ser [ERROR] Error in Cobertura Report generation: Unable to generate Cobertura Report for project. [ERROR] Oct 30, 2013 5:28:56 PM net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler loadCoverageData Error: Unable to read from data file /x/workspace/jenkinsjob/projects/domain/domain-project/target/cobertura/cobertura.ser [ERROR] Error in Cobertura Report generation: Unable to generate Cobertura Report for project. |
Just an update. Were too experiencing the same problem... And couldn't get it work with cobertura-maven-plugin version 2.6. However tried using cobertura-maven-plugin version 2.5.2 as an experiment. And to my surprise, the code coverage showed up. Am using recent java version 1.7.0_40. Have put my plugins configuration below. Although this is just a workaround, and not a final solution, thought this might be of some help not only to its users, but also for cobertura-maven-plugin developers.
:-) |
And more info... While using 2.5.2 i see some parse exception in the output.
When i went to that line, i saw the new feature of generics used in that line.
Think where version 2.5.2 although gives an error and generates reports, 2.6 version fails in that line... May or may not be true. But just a thought. Sreram |
@dmehra I'm getting same ERROR message although report generation works fine, did you end up creating another ticket for that scenario? cobertura-maven-plugin version: 2.5.2 |
@parxier I didn't file a separate ticket since it was a cosmetic issue for me. |
I have the same issue, EOFException, and found it happens depending of how many tests are run. Instrumenting 2086 files running 92 tests fails with the error above, where as instrumenting the same number of classes and running 82 tests succeeds. This is reproducible each and every time. Environment: Found a similar issue here http://markmail.org/message/o6e3koq2sy3kdiqg#query:+page:1+mid:jliqwosbup7oagr6+state:results |
I was able to overcome this error by increasing JVM memory options. I no longer see the EOF exception. Cobertura should have a better message in these cases. Here's my MAVEN_OPTS -Xms1024m |
Thanks maskbit I tried increasing the JVM options as part of the surefire JVM config
Got the same error. But I noticed during the run the java process only took up 600MB. So I am not sure if it is a memory issue or a timing issue, where the JVM shutdown is not giving cobertura enough time to write out to the cobertura.ser file. I created a new cobertura issue for this item. |
I had the same problem and in my case, downgrading the version from 2.6 to 2.5.2 fixed the problem. |
Regarding the comments on the logged error with nonetheless successful report generation: #130 addresses this issue. |
This is biting me too. Downgrading from 2.6 to 2.5.2 gave me different errors (even increasing the memory did not fix this). Perhaps cobertura is having trouble parsing generics within generics? Here is my stack trace: |
I am using jav 8 and had same issue as @grayaii while downgrading Any luck? |
Could someone please try this using Cobertura 2.1.1 or Cobertura Maven Plugin 2.7? |
@dennisl I gave it a try just now. Worked like a charm! No more useless |
@ckarawani Thank you for testing! |
Cobertura does not report coverage in Sonar for this project. I find the below error in jenkins log.
Using Java7 and Cobertura 2.0.3
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ domain-project ---[ERROR] Oct 29, 2013 4:23:53 PM net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler saveCoverageData
INFO: Cobertura: Saved information on 203 classes.
[INFO] Instrumentation was successful.
[INFO] NOT adding cobertura ser file to attached artifacts list.
INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ domain-payment ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[ERROR] Oct 29, 2013 4:37:20 PM net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler loadCoverageData
SEVERE: Cobertura: Error reading file /x/Mobile/projects/domain/domain-project/target/cobertura/cobertura.ser: null
java.io.EOFException
The text was updated successfully, but these errors were encountered: