[
https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286744#comment-13286744
]
Steven Rowe commented on LUCENE-4092:
-------------------------------------
I plan on adding the following (as suggested by Robert) as alternations to the
BUILD_LOG_REGEX for all non-Maven Jenkins jobs (some of these things don't run
under the Maven jobs, and Maven's output is different enough that it'll require
separate treatment):
bq. the javadocs warnings task
{noformat}
(?:[^\r\n]*\[javadoc\].*\r?\n)*[^\r\n]*\[javadoc\]\s*[1-9]\d*\s+warnings.*\r?\n
{noformat}
bq. two javadocs checkers in javadocs-lint
Output from javadocs-lint seems to show up only when there's a problem, so any
output from it will always be extracted by the following regex:
{noformat}
[^\r\n]*javadocs-lint:.*\r?\n(?:[^\r\n]*\[echo\].*\r?\n)*
{noformat}
bq. and the rat-checker
{noformat}
[^\r\n]*rat-sources:\s+\[echo\].*(?:\r?\n[^\r\n]*\[echo\].*)*\s*[1-9]\d*\s+Unknown\s+Licenses.*\r?\n(?:[^\r\n]*\[echo\].*\r?\n)*
{noformat}
Along with two others:
# Compilation failures:
{noformat}
(?:[^\r\n]*\[javac\].*\r?\n)*[^\r\n]*\[javac\]\s*[1-9]\d*\s*error.*\r?\n
{noformat}
# Jenkins FATAL errors:
{noformat}
[^\r\n]*FATAL:(?s:.*)
{noformat}
> Check what's Jenkins pattern for e-mailing log fragments (so that it includes
> failures).
> ----------------------------------------------------------------------------------------
>
> Key: LUCENE-4092
> URL: https://issues.apache.org/jira/browse/LUCENE-4092
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: general/test
> Reporter: Dawid Weiss
> Priority: Trivial
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
