You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Andrey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/05/23 11:35:00 UTC
[jira] [Created] (IGNITE-8570) Create lighter version of
GridStringLogger
Andrey Kuznetsov created IGNITE-8570:
----------------------------------------
Summary: Create lighter version of GridStringLogger
Key: IGNITE-8570
URL: https://issues.apache.org/jira/browse/IGNITE-8570
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.4
Reporter: Andrey Kuznetsov
Fix For: 2.6
Most usages of {{GridStringLogger}} in test assumes the following scenario. First, it is set as a logger for some Ignite node. Then, after some activity on that node, log content is searched for some predefined strings. {{GridStringLogger}} uses {{StringBuilder}} of bounded size internally to store log contents, older contents gets dropped on exaustion. Thus, changes that add more logging may damage some independent tests that use {{GridStringLogger}}.
The suggestion is to implement and use another test logger conforming to these requirements:
* It does not accumulate any logs.
* It allows to set the listener that fires when log message matches certain regular expression, {{Matcher}} can be passed to the listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)