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

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

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            thetaphi 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

            Show
            thetaphi 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
            Hide
            kohsuke 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.

            Show
            kohsuke 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.
            Hide
            rshelley 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.

            Show
            rshelley 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.
            Hide
            rogerzhang Roger Zhang added a comment -

            Does anyone know when this problem will be resolved?

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

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

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

              People

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

                Dates

                Created:
                Updated:
                Resolved: