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

Console output incorrect if log contains HTML-like structures

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • Hudson 1.349

      When the build log contains structures like "<SOMETHING>" or "<<SOMETHING>>", the output becomes "" or "<>". This applies to all browsers (tested with Firefox 3.6, Safari 4, Chrome).

      In Firefox 3.6, HTML-like structures can also truncate the log, i.e. the log is only shown up to before the offending text. This doesn't happen with every occurrence of a "<...>" pattern, but for example this breaks it:

      2010-03-10 13:49:39,978 DEBUG – 1 result(s) from test_department in 1 ms. <<T[8672,MC,UC,C[9,RC,users=1,reuses=166,sets=0,pool=transactional-read]]>>

      Workaround: use the plain text console log instead.

          [JENKINS-5907] Console output incorrect if log contains HTML-like structures

          lptr created issue -
          lptr made changes -
          Description Original: When the build log contains structures like "<SOMETHING>" or "<<SOMETHING>>", the output becomes "" or "<>". This applies to all browsers (tested with Firefix 3.6, Safari 4, Chrome).

          In Firefox 3.6, HTML-like structures can also truncate the log, i.e. the log is only shown up to before the offending text. This doesn't happen with every occurrence of a "<...>" pattern, but for example this breaks it:

          2010-03-10 13:49:39,978 DEBUG -- 1 result(s) from test_department in 1 ms. <<T[8672,MC,UC,C[9,RC,users=1,reuses=166,sets=0,pool=transactional-read]]>>

          Workaround: use the plain text console log instead.
          New: When the build log contains structures like "<SOMETHING>" or "<<SOMETHING>>", the output becomes "" or "<>". This applies to all browsers (tested with Firefox 3.6, Safari 4, Chrome).

          In Firefox 3.6, HTML-like structures can also truncate the log, i.e. the log is only shown up to before the offending text. This doesn't happen with every occurrence of a "<...>" pattern, but for example this breaks it:

          2010-03-10 13:49:39,978 DEBUG -- 1 result(s) from test_department in 1 ms. <<T[8672,MC,UC,C[9,RC,users=1,reuses=166,sets=0,pool=transactional-read]]>>

          Workaround: use the plain text console log instead.
          Andrew Bayer made changes -
          Link New: This issue duplicates JENKINS-5852 [ JENKINS-5852 ]
          Andrew Bayer made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: www [ 15484 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135999 ] New: JNJira + In-Review [ 203794 ]

            Unassigned Unassigned
            lptr lptr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: