Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7836

Clover and cobertura parsing on hudson master fails because of invalid XML

      Since a few days, on our Apache Hudson installation, parsing of Clover's clover.xml or the Coberture's coverage.xml file fails (but not in all cases, sometimes it simply passes with the same build and same job configuration). This only happens after transferring to master, the reports and xml file is created on Hudson slave. It seems like the network code somehow breaks the xml file during transfer to the master.

      Downloading th clover.xml from the workspace to my local computer and validating it confirms, that it is not incorrectly formatted and has no XML parse errors.

          [JENKINS-7836] Clover and cobertura parsing on hudson master fails because of invalid XML

          Code changed in jenkins
          User: Jerome Lacoste
          Path:
          remoting/src/main/java/hudson/remoting/ProxyInputStream.java
          http://jenkins-ci.org/commit/core/31b8361d3152fb7970e1c11c906a763fa1aa5c25
          Log:
          JENKINS-7836 tentative fix for the copy from slave to master issues. The problem looks similar to JENKINS-7745, so we might as well synchronized the ProxyInputStream.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jerome Lacoste Path: remoting/src/main/java/hudson/remoting/ProxyInputStream.java http://jenkins-ci.org/commit/core/31b8361d3152fb7970e1c11c906a763fa1aa5c25 Log: JENKINS-7836 tentative fix for the copy from slave to master issues. The problem looks similar to JENKINS-7745 , so we might as well synchronized the ProxyInputStream.

          Uwe Schindler added a comment -

          Hi Jerome,
          thanks for the work done. As Apache is planning to move over to Jenkins, we hope to solve this soon. Please keep me informed, when a new release containing this fix is done!

          Uwe Schindler added a comment - Hi Jerome, thanks for the work done. As Apache is planning to move over to Jenkins, we hope to solve this soon. Please keep me informed, when a new release containing this fix is done!

          Hi Jerome,

          I have built:
          https://github.com/jenkinsci/jenkins/commit/c15378ef53bbcbaac1df11662ac4e16d28a008ea
          Where your fix is included but actually it only seams to get worse with this build.

          (The only change I have made is to use jmdns-3.4.0 instead of the "bundled" version, see http://issues.hudson-ci.org/browse/HUDSON-8647)

          If you need any information (logs, stats, dumps) or if I can run any experimental code for you to help resolve this issue send me an e-mail at rickard.von.essen 'at' gmail.com

          Rickard von Essen added a comment - Hi Jerome, I have built: https://github.com/jenkinsci/jenkins/commit/c15378ef53bbcbaac1df11662ac4e16d28a008ea Where your fix is included but actually it only seams to get worse with this build. (The only change I have made is to use jmdns-3.4.0 instead of the "bundled" version, see http://issues.hudson-ci.org/browse/HUDSON-8647 ) If you need any information (logs, stats, dumps) or if I can run any experimental code for you to help resolve this issue send me an e-mail at rickard.von.essen 'at' gmail.com

          robertredd added a comment -

          I can confirm this issue is still present in 1.398. I had thought some of the other related cases may have resolved it, but it hasn't. I just wanted to confirm it's still an issue that I know is being worked on. Out of about 80 builds I run at night for statistics, about 10 will fail with this error.

          robertredd added a comment - I can confirm this issue is still present in 1.398. I had thought some of the other related cases may have resolved it, but it hasn't. I just wanted to confirm it's still an issue that I know is being worked on. Out of about 80 builds I run at night for statistics, about 10 will fail with this error.

          Cody Cutrer added a comment -

          I also just experienced it again on 1.397, though with a much lower frequency than pre-1.397.

          Cody Cutrer added a comment - I also just experienced it again on 1.397, though with a much lower frequency than pre-1.397.

          oeuftete added a comment -

          Still an issue in 1.399 (which included the fix for JENKINS-7809... so I guess that wasn't it).

          oeuftete added a comment - Still an issue in 1.399 (which included the fix for JENKINS-7809 ... so I guess that wasn't it).

          Roger Zhang added a comment -

          Does anyone know when this problem will be resolved?

          Roger Zhang added a comment - Does anyone know when this problem will be resolved?

          rshelley added a comment -

          To work around this, I've setup Sonar and am pushing all my code quality reports to it instead of reporting it in Jenkins. Even if this gets fixed, I doubt I'll go back, Sonar is just too nice and useful.

          rshelley added a comment - To work around this, I've setup Sonar and am pushing all my code quality reports to it instead of reporting it in Jenkins. Even if this gets fixed, I doubt I'll go back, Sonar is just too nice and useful.

          The links in the original description of this issue are no longer working, so I cannot be sure of the failure mode that the reporter saw. As such, I'm also unclear what later "me, too" comments are referring to.

          Now, I've just committed a fix to JENKINS-7871 toward 1.402, and I suspect that fixes this issue as well.

          If you continue to see a problem after 1.402, please open a separate issue, or reopen JENKINS-7871 (provided that the failure mode is the same), instead of reopening this issue, since it's unclear exactly what this issue is referring to.

          Kohsuke Kawaguchi added a comment - The links in the original description of this issue are no longer working, so I cannot be sure of the failure mode that the reporter saw. As such, I'm also unclear what later "me, too" comments are referring to. Now, I've just committed a fix to JENKINS-7871 toward 1.402, and I suspect that fixes this issue as well. If you continue to see a problem after 1.402, please open a separate issue, or reopen JENKINS-7871 (provided that the failure mode is the same), instead of reopening this issue, since it's unclear exactly what this issue is referring to.

          Uwe Schindler added a comment -

          The links are no longer working, but the field "URL", still shows the issue in the apache mailing list: http://mail-archives.apache.org/mod_mbox/www-builds/201010.mbox/%3c007b01cb6af6$e5f74e00$b1e5ea00$@thetaphi.de%3e

          Uwe Schindler added a comment - The links are no longer working, but the field "URL", still shows the issue in the apache mailing list: http://mail-archives.apache.org/mod_mbox/www-builds/201010.mbox/%3c007b01cb6af6$e5f74e00$b1e5ea00$@thetaphi.de%3e

            kohsuke Kohsuke Kawaguchi
            thetaphi Uwe Schindler
            Votes:
            68 Vote for this issue
            Watchers:
            65 Start watching this issue

              Created:
              Updated:
              Resolved: