[
https://issues.apache.org/jira/browse/KAFKA-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014665#comment-15014665
]
Geoff Anderson commented on KAFKA-2861:
---------------------------------------
[~ewencp] Good point, I'm not sure if this is workable generically.
This falls into the category of: how do we surface things or events that seem
to be bad, but not bad in some expected way? How do we increase the probability
that we'll catch anomalous behavior without creating false failures?
> 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)
