Home > Cannot Parse > Cannot Parse Coverage Results

Cannot Parse Coverage Results

Show jieryn added a comment - 2009/Sep/10 7:14 PM I see this too with Hudson 1.323 and Hudson Cobertura 0.8.9. What are the applications of taking the output of an amp with a microphone? at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:684) at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:369) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1742) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.arrangeCapacity(XMLEntityScanner.java:1619) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipString(XMLEntityScanner.java:1657) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:193) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at hudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:77) at hudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:48) at share|improve this answer edited Jun 18 '12 at 7:31 answered Oct 19 '10 at 13:04 Patrick from NDepend team 8,9973451 add a comment| up vote -1 down vote I use NCover weblink

Hide Permalink jieryn added a comment - 2009/Sep/10 7:14 PM I see this too with Hudson 1.323 and Hudson Cobertura 0.8.9. FATAL: Unable to parse /d1/hudson/jobs/trunk-continuous/builds/2009-08-18_16-24-48/coverage3259.xml com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. None of these code is exposed via API outside remoting, so at some point we can revert this change to simplify the code a bit and eliminate the redundancy, because as If you agree to our use of cookies, please close this message and continue to use this site. https://issues.jenkins-ci.org/browse/JENKINS-11251

Hide Permalink SCM/JIRA link daemon added a comment - 2012/Jun/16 2:36 AM Code changed in jenkins User: Kohsuke Kawaguchi Path: src/test/java/hudson/remoting/PipeWriterTest.java src/test/java/hudson/remoting/PipeWriterTestChecker.java src/test/java/hudson/remoting/RmiTestBase.java http://jenkins-ci.org/commit/remoting/00609519a68bb2b488d6217d49f53a76d955bed0 Log: Added a test case for JENKINS-11251. What is with the speech audience? FATAL: Unable to parse /home/cruise/opt/hudson-work/jobs/trunk_libs/builds/2010-10-29_07-50-35/coverage6.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) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:558) at hudson.model.Build$RunnerImpl.post2(Build.java:157) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1304) at

The file is 9945 lines long and 7880 get transferred. Did you generate the XML > report(s) for Cobertura? > Build step 'Publish Cobertura Coverage Report' changed build result to > FAILURE > Recording test results > What happened here is Publishing Cobertura coverage results... at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipSpaces(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown Source) at

If I kick the job off again without changing anything it passes. Hide Permalink maxence added a comment - 2010/Nov/28 6:01 AM Same here, occurs with Hudson 1.384 on JDK 1.6.0_u22, with master running Debian 5.0 and slave running Ubuntu 10.04. Has anyone else seen this problem or have any ideas? Check This Out 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) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at hudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:77) ...

Works quite well and does not require complex activities, can be easily included in the build process. It takes a .coverage file as input and can export it to clover or html. Closed is related to JENKINS-7871 "java.io.IOException: Bad file descriptor" when file copied from slave Resolved JENKINS-9189 truncation or corruption of zip workspace archive from slave Resolved Activity All Comments History Activity This is my pillow How Did The Dred Scott Decision Contribute to the Civil War?

What now? People Assignee: Stephen Connolly Reporter: moizd Votes: 5 Vote for this issue Watchers: 6 Start watching this issue Dates Created: 2009/Aug/18 4:37 PM Updated: 2016/Jul/13 9:05 AM Resolved: 2011/Jul/12 9:45 AM Hide Permalink hudsonfsc added a comment - 2010/Nov/25 3:09 AM - edited We also have the same problem on a different version/environment. The maven build had completed successfully.

You can also write and apply continuously code rules written over LINQ queries (CQLinq) like: From now, all types added or refactored should be 100% covered by tests // From now, have a peek at these guys Show sogabe added a comment - 2011/Jul/12 9:45 AM reopen if reproduced. Join This Project Subprojects Hudson CI Infrastructure Hudson CI Plugins Feedback FAQ Terms of Use Privacy Trademarks Your use of this web site or any of its content or software indicates Take a tour to get the most out of Samebug.

Try JIRA - bug tracking software for your team. Show JP Rosevear added a comment - 2014/Feb/15 12:03 AM Without the coverage file, this is not possible to resolve sanely. FATAL: Unable to parse /opt/hudson/.hudson/jobs/Bob Pipeline/builds/2010-12-10_19-10-01/coverage7.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) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:603) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:582) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:651) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:529) at hudson.model.Run.run(Run.java:1363) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:349) http://scriptkeeper.net/cannot-parse/cannot-parse-coverage-results-jenkins.html Show moizd added a comment - 2009/Aug/18 4:55 PM It appears that the coverage xml files are in binary format.

Can I just copy the coverage.xml file myself at the end of the build in hopes that jenkins will see that and not try to copy a file it is going 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) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1411) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:902) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:605) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1393) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1763) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipSpaces(XMLEntityScanner.java:1543) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1375) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1310) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at Compare: https://github.com/jenkinsci/remoting/compare/cb1854b81ac8...00609519a68b Show SCM/JIRA link daemon added a comment - 2012/Jun/16 2:36 AM Code changed in jenkins User: Kohsuke Kawaguchi Path: src/test/java/hudson/remoting/PipeWriterTest.java src/test/java/hudson/remoting/PipeWriterTestChecker.java src/test/java/hudson/remoting/RmiTestBase.java http://jenkins-ci.org/commit/remoting/00609519a68bb2b488d6217d49f53a76d955bed0 Log: Added a test case for

AttachmentsIssue Links duplicates JENKINS-7836 Clover and cobertura parsing on hudson master fails because of invalid XML Resolved is duplicated by JENKINS-7836 Clover and cobertura parsing on hudson master fails because of

Hide Permalink Sagar Khushalani added a comment - 2011/Jan/19 6:14 AM Same here, occurs on 1.392, JDK 1.6.0_19, both master and slave are linux. How?3How do I get Visual Studio to display code coverage results for dlls with 0% code coverage?19PostSharp and Visual Studio Code Coverage4Code Coverage Visual Studio 20101code coverage with visual studio and Now, I'd like to be able to view that code coverage data outside of visual studio, say in a web browser. If I kick the job off again without changing anything it passes.

Atlassian Jenkins CI › Jenkins users Search everywhere only in this topic Advanced Search Cobertura Plugin fails to parse coverage.xml ‹ Previous Topic Next Topic › Classic List Threaded ♦ DashboardsProjectsIssuesCaptureGetting started Help JIRA Core help Keyboard Shortcuts About JIRA JIRA Credits Log In Register for Jenkins World Join the Jenkins community at "Jenkins World" in Santa Clara, California from September Jenkins JIRA | 6 years ago | flyasaurus hudson.util.IOException2: Cannot parse coverage results find similars Java RT hudson.plugins.cobertura Hudson Hudson Maven Embedder Hudson 0 0 mark Here is the post build this content Thanks a lot, Frederic AttachmentsIssue Links is duplicated by JENKINS-6609 Fitnesse publisher plugin fails to parse XML file.

Subject: [JIRA] Commented: (HUDSON-7951) Build fails on parsing coverage.xml Date: Thu, 4 Nov 2010 08:46:30 -0800 (PST) Mailing-list: contact [email protected]; run by ezmlm [ http://issues.hudson-ci.org/browse/HUDSON-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143279#action_143279 ] robhruskacommentedonHUDSON-7951: ----------------------------------- Thisisprobablyrelatedtohttp://issues.hudson-ci.org/browse/HUDSON-7951 andhttp://issues.hudson-ci.org/browse/HUDSON-7836 >Buildfailsonparsingcoverage.xml Automated exception search integrated into your IDE Test Samebug Integration for IntelliJ IDEA 0 mark [JENKINS-7871] "java.io.IOException: Bad file descriptor" when file copied from slave - Jenkins JIRA jenkins-ci.org | 3 Publishing Cobertura coverage results... Jenkins - 1.399 cobertura plugin - 1.2 stacktrace: FATAL: Unable to parse c:\hudson_work\jobs\app-dp-edit-Trunk\builds\2011-05-20_22-49-55\coverage.xmlhudson.util.IOException2: Cannot parse coverage results athudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:89)athudson.plugins.cobertura.CoberturaCoverageParser.parse(CoberturaCoverageParser.java:52)athudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:265)athudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)athudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:644)athudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:623)athudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:601)athudson.model.Build$RunnerImpl.post2(Build.java:159)athudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:570)athudson.model.Run.run(Run.java:1386)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)athudson.model.ResourceController.execute(ResourceController.java:88)athudson.model.Executor.run(Executor.java:145)Caused by:org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.

share|improve this answer edited Jan 18 '13 at 7:40 JacobE 4,25043045 answered Sep 29 '12 at 19:44 Luke Syvil 613 add a comment| up vote 0 down vote I can't speak Master = CentOS 5.4, Slave = Mandriva 2010.1 Show Sagar Khushalani added a comment - 2011/Jan/19 6:14 AM Same here, occurs on 1.392, JDK 1.6.0_19, both master and slave are linux. Show hudsonfsc added a comment - 2010/Nov/25 3:09 AM - edited We also have the same problem on a different version/environment. I got the coverage.xml from the workspace of a failed build and then from the workspace after I re-ran it and it passed and compared them and they were exactly the