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

Spurious debugging information written to Hudson console in 1.334

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • build-timeout-plugin
    • None
    • Platform: All, OS: All

      In Hudson 1.334, the Hudson console log shows spurious outout that looks like
      debugging information that was left in, possibly in some plugin. Not a major
      problem, but probably should not be there. Here's some sample output:

      Constructor called: 60 true
      Constructor called: 60 true
      Constructor called: 60 true
      Constructor called: 60 true
      Constructor called: 120 true
      18-Nov-2009 15:25:47 hudson.triggers.SCMTrigger$Runner run
      INFO: SCM changes detected in GDA_trunk.core. Triggering #1432
      18-Nov-2009 15:25:51 hudson.model.Run run
      INFO: GDA_8.0.simulation.b16 #9 main build action completed: FAILURE
      Constructor called: 60 true
      Constructor called: 60 true
      Constructor called: 60 true
      Constructor called: 60 true

          [JENKINS-4891] Spurious debugging information written to Hudson console in 1.334

          Matthew Webber created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 134964 ] New: JNJira + In-Review [ 203176 ]

            mindless Alan Harder
            mwebber Matthew Webber
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: