You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2018/10/04 18:51:00 UTC
[jira] [Updated] (GEODE-5827) DUnit suspect string setUp is
generating ERROR messages
[ https://issues.apache.org/jira/browse/GEODE-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk Lund updated GEODE-5827:
-----------------------------
Priority: Trivial (was: Major)
> DUnit suspect string setUp is generating ERROR messages
> -------------------------------------------------------
>
> Key: GEODE-5827
> URL: https://issues.apache.org/jira/browse/GEODE-5827
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Kirk Lund
> Priority: Trivial
>
> The ERROR messages are generated because hexTid is a custom PatternConverter. DUnit is programmatically adding an Appender for suspect string detection and there doesn't seem to be a way to add custom PatternConverter. We'll probably have to use tid instead of hexTid for the suspect string detection appender.
> {noformat}
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized format specifier [hexTid]
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized conversion specifier [hexTid] starting at position 78 in conversion pattern.
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized format specifier [hexTid]
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized conversion specifier [hexTid] starting at position 78 in conversion pattern.
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier [hexTid]
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier [hexTid] starting at position 78 in conversion pattern.
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier [hexTid]
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier [hexTid] starting at position 78 in conversion pattern.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)