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

Meaningless log message org.jenkinsci.plugins.xunit.XUnitProcessorResult@50f463dd

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • xunit-plugin
    • None
    • Jenkins 2.378
      xunit plugin 3.1.2
    • 3.1.3

      Can this message be made more human readable? What does org.jenkinsci.plugins.xunit.XUnitProcessorResult@50f463dd mean?

      INFO: Setting the build status to org.jenkinsci.plugins.xunit.XUnitProcessorResult@50f463dd
      

          [JENKINS-70113] Meaningless log message org.jenkinsci.plugins.xunit.XUnitProcessorResult@50f463dd

          Dave E added a comment -

          Possibly a mistake on line 239 of XUnitPublisher.java : https://github.com/jenkinsci/xunit-plugin/blob/66e06d2d02e9d32212aec8f853d56b71f6f04d99/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L239

          It should probably read:

          logger.info("Setting the build status to " + procResult);

          Dave E added a comment - Possibly a mistake on line 239 of XUnitPublisher.java : https://github.com/jenkinsci/xunit-plugin/blob/66e06d2d02e9d32212aec8f853d56b71f6f04d99/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L239 It should probably read: logger.info("Setting the build status to " + procResult);

          Yeah, good catch. Looks like a regression in commit 66e06d2d02e9d32212aec8f853d56b71f6f04d99.

          Davide Pesavento added a comment - Yeah, good catch. Looks like a regression in commit 66e06d2d02e9d32212aec8f853d56b71f6f04d99 .

          Beni Peled added a comment -

          Fixed on https://github.com/jenkinsci/xunit-plugin/pull/100

          Waiting for the next release...

          Beni Peled added a comment - Fixed on https://github.com/jenkinsci/xunit-plugin/pull/100 Waiting for the next release...

            nfalco Nikolas Falco
            pesa Davide Pesavento
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: