[
https://issues.apache.org/jira/browse/GEODE-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185640#comment-15185640
]
John Blum commented on GEODE-1052:
----------------------------------
Why not just do the following...
{{$gradlew ... -Dgemfire.log-level=config ...}}
Of course, this probably won't propagate to all test VMs forked and started by
the DUnit test container. However, it is a simple matter to propagate System
properties to other VMs forked by the build & test VM, much like the _Gfsh_
{{start[Locator|Server]}} commands do today when forking a GemFire member
process VM.
Plus, using actual GemFire System properties for configuration at testing as
well as runtime will reinforce the public interface of GemFire, which include
the properties.
> enable specifying logLevel as a system property in command line for dunit test
> ------------------------------------------------------------------------------
>
> Key: GEODE-1052
> URL: https://issues.apache.org/jira/browse/GEODE-1052
> Project: Geode
> Issue Type: Test
> Reporter: xiaojian zhou
> Assignee: xiaojian zhou
> Fix For: 1.0.0-incubating.M2
>
>
> To run a dunit test, we current need to modify the test code to specify
> loglevel, otherwise it's "info".
> It's better to specify the logLevel to be used by the test in gradle command
> line, such as
> ./gradlew --no-daemon geode-core:distributedTest -DlogLevel=debug
> -DdistributedTest.single=PutAllCSDUnitTest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
