Every "distributed" unit test I've run lately has had it. I just tried
ClusterCommunicationsDUnitTest. createEntryAndVerifyUpdate(), for instance, and
see these ERRORs in the output. For some reason the test runner ignores these
messages and the tests pass.
On 2/24/21, 4:07 PM, "Udo Kohlmeye
What test(s) are you running? Version?
--Udo
On 2/25/21, 8:39 AM, "Ernie Burghardt" wrote:
Its not just you Bruce, I get this...
2021-02-24 13:38:10,891 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Error p
Its not just you Bruce, I get this...
2021-02-24 13:38:10,891 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Error processing element GeodeLogWriter
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Er
This has started showing up in all of my test runs. Is anyone else seeing it?
Maybe something in my environment?
2021-02-24 11:19:44,765 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 11:19:44,778 main ERROR Error processing element GeodeLogWri
