Trim JUnit stack traces & logs to reasonable length before mailing

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      $FAILED_TESTS includes full stdout/stderr of tests and stack traces. If you are using something like

      http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-nbjunit/org/netbeans/junit/NbTestCase.html#logLevel%28%29

      these can be quite large. Furthermore, sometimes complete text of a log session is packed into a single line of text (no internal newlines), and when replying to such a message, Thunderbird has extremely poor performance.

      Better to truncate all this to some reasonable maximum sizes, as we do for e.g. console logs; the user can always click the hyperlink to the build's test cases to see details.

            Assignee:
            Alex Earl
            Reporter:
            Jesse Glick
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: