You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2016/03/15 19:00:37 UTC
[jira] [Resolved] (GEODE-1097) allow Lambda invocations to be named
so that they show up in test logs
[ https://issues.apache.org/jira/browse/GEODE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt resolved GEODE-1097.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M2
> allow Lambda invocations to be named so that they show up in test logs
> ----------------------------------------------------------------------
>
> Key: GEODE-1097
> URL: https://issues.apache.org/jira/browse/GEODE-1097
> Project: Geode
> Issue Type: Improvement
> Components: tests
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Fix For: 1.0.0-incubating.M2
>
>
> Currently lambda invocations are logged like this:
> [vm_1][info 2016/03/14 10:17:04.395 PDT <RMI TCP Connection(1)-10.118.33.195> tid=0x14] Received method: com.gemstone.gemfire.test.dunit.DurableClientSimpleDUnitTest$$Lambda$5/1964980796.run with 0 args on object: com.gemstone.gemfire.test.dunit.DurableClientSimpleDUnitTest$$Lambda$5/1964980796@5e43dcd9
> It would be helpful to be able to have more context than this logged, such as
> [vm_0][info 2016/03/14 15:30:36.314 PDT <RMI TCP Connection(1)-10.118.33.195> tid=0x14] Received method: com.gemstone.gemfire.test.dunit.NamedCallable.call with 0 args on object: callable(getTestGetNotifiedClients_port)
> so that we can tell what the Lambda is doing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)