[
https://issues.apache.org/jira/browse/KAFKA-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013227#comment-15013227
]
Ewen Cheslack-Postava commented on KAFKA-2861:
----------------------------------------------
[~geoffra] Of course, the problem with this is that if you intentionally
trigger an error you'll also fail the test...
I've thought about this before, but it's really difficult to generically detect
these issues -- log levels aren't good enough, trying to find stack traces
(i.e. logging an exception) doesn't work, etc.
> system tests: grep logs for errors as part of validation
> --------------------------------------------------------
>
> Key: KAFKA-2861
> URL: https://issues.apache.org/jira/browse/KAFKA-2861
> Project: Kafka
> Issue Type: Bug
> Reporter: Geoff Anderson
>
> There may be errors going on under the hood that validation steps do not
> detect, but which are logged at the ERROR level by brokers or clients. We are
> more likely to catch subtle issues if we pattern match the server log for
> ERROR as part of validation, and fail the test in this case.
> For example, in https://issues.apache.org/jira/browse/KAFKA-2813, the error
> is transient, so our test may pass; however, we still want this issue to be
> visible.
> To avoid spurious failures, we would probably want to be able to have a
> whitelist of acceptable errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
