[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

[sar...@syr.edu (JIRA)]

Steve Rowe commented on JENKINS-14132 Very long content token string parameter triggers a StackOverflowError Configuration that triggers the bug: Build: ${BUILD_URL} ${FAILED_TESTS} Build Log: ${BUILD_LOG_MULTILINE_REGEX,regex="(?x: \ \ # Compilation failures (possessive quantifier on '*+' prevents backtracking and reduces stack usage) \ (?:.*\\[javac\\]\\s++(?![1-9]\\d*\\s+error).*\\r?\\n)*+.*\\[javac\\]\\s+[1-9]\\d*\\s+error.*\\r?\\n \ \ # Test failures (possessive quantifier on '*+' prevents backtracking and reduces stack usage) \ |.*\\[junit4\\]\\s+Suite:.*+\\s++.*\\[junit4\\]\\s++(?!Completed)(?!IGNOR).*\\r?\\n \ (?:.*\\[junit4\\]\\s++(?!Completed\\s+on.*<<<\\s*FAILURES!).*\\r?\\n)*+ \ .*\\[junit4\\]\\s++Completed\\s+on.*<<<\\s*FAILURES!\\r?\\n \ \ # Source file license problems (possessive quantifier on '*+' prevents backtracking and reduces stack usage) \ |.*rat-sources:.*\\r?\\n(?:.*\\[echo\\]\\s++(?![1-9]\\d*\\s+Unknown\\s+Licenses).*\\r?\\n)*+ \ .*\\[echo\\]\\s+[1-9]\\d*\\s+Unknown\\s+Licenses.*\\r?\\n(?:.*\\[echo\\].*\\r?\\n)*+ \ \ # Third-party dependency license problems - include 2 preceding lines and 1 following line \ |(?:.*\\r?\\n){2}.*\\[licenses\\]\\s+MISSING\\s+sha1(?:.*\\r?\\n){2} \ \ # Javadoc warnings (possessive quantifier on '*+' prevents backtracking and reduces stack usage) \ |(?:.*\\[javadoc\\]\\s++(?![1-9]\\d*\\s+warnings).*\\r?\\n)*+.*\\[javadoc\\]\\s*[1-9]\\d*\\s+warnings.*\\r?\\n \ \ # Other javadocs problems: broken links and missing javadocs \ |.*javadocs-lint:.*\\r?\\n(?:.*\\[echo\\].*\\r?\n)*+ \ \ # Thread dumps - include 1 preceding line and the remainder of the log \ |.*\\r?\\n.*Full\\s+thread\\s+dump(?s:.*+) \ \ # Jenkins problems - include the remainder of the log \ |.*(?:FATAL|ERROR):(?s:.*+) \ \ # The Ant call stack - include the remainder of the log \ |.*BUILD\\s+FAILED(?s:.*+) \ )"}

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira