Mailing-List: contact issues-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Wed, 28 Jun 2017 23:02:00 +0000 (UTC)
From: "Jared Stewart (JIRA)" <jira@apache.org>
To: issues@geode.apache.org
Message-ID: <JIRA.13080878.1497889919000.129361.1498690920244@Atlassian.JIRA>
In-Reply-To: <JIRA.13080878.1497889919000@Atlassian.JIRA>
References: <JIRA.13080878.1497889919000@Atlassian.JIRA> <JIRA.13080878.1497889919645@jira-lw-us.apache.org>
Subject: [jira] [Updated] (GEODE-3103) GfshRule clutters the nightly build
 output
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 28 Jun 2017 23:02:06 -0000


     [ https://issues.apache.org/jira/browse/GEODE-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jared Stewart updated GEODE-3103:
---------------------------------
    Fix Version/s: 1.3.0

> GfshRule clutters the nightly build output
> ------------------------------------------
>
>                 Key: GEODE-3103
>                 URL: https://issues.apache.org/jira/browse/GEODE-3103
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh, tests
>            Reporter: Jared Stewart
>            Assignee: Jared Stewart
>             Fix For: 1.3.0
>
>
> Most tests only write output to the nightly build when they fail.  Right now the GfshRule is piping the output from the Gfsh processes it starts into System.out which results in cluttered nightly build logs:
> ```
> :geode-assembly:build
> :geode-assembly:distributedTest
> (1) Executing - start locator --name=locator1
> ....
> Locator in /tmp/junit7008076194550925969/locator1 on penates.apache.org[10334] as locator1 is currently online.
> Process ID: 1678
> Uptime: 4 seconds
> Geode Version: 1.3.0-SNAPSHOT
> Java Version: 1.8.0_131
> Log File: /tmp/junit7008076194550925969/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: <https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-core-1.3.0-SNAPSHOT.jar>:<https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar>
> Successfully connected to: JMX Manager [host=penates.apache.org, port=1099]
> Cluster configuration service is up and running.
> (1) Executing - connect
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=penates.apache.org, port=1099] ..
> Successfully connected to: [host=penates.apache.org, port=1099]
> (2) Executing - status locator --name=locator1
> Locator in /tmp/junit7008076194550925969/locator1 on penates.apache.org[10334] as locator1 is currently online.
> Process ID: 1678
> Uptime: 18 seconds
> Geode Version: 1.3.0-SNAPSHOT
> Java Version: 1.8.0_131
> Log File: /tmp/junit7008076194550925969/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: <https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-core-1.3.0-SNAPSHOT.jar>:<https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar>
> Cluster configuration service is up and running.
> (1) Executing - stop locator --dir=/tmp/junit7008076194550925969/locator1
> ..
> (1) Executing - start locator --name=locator1
> ....
> Locator in /tmp/junit6693528666226757220/locator1 on penates.apache.org[10334] as locator1 is currently online.
> Process ID: 2996
> Uptime: 3 seconds
> Geode Version: 1.3.0-SNAPSHOT
> Java Version: 1.8.0_131
> Log File: /tmp/junit6693528666226757220/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: <https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-core-1.3.0-SNAPSHOT.jar>:<https://builds.apache.org/job/Geode-nightly/870/artifact/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar>
> Successfully connected to: JMX Manager [host=penates.apache.org, port=1099]
> Cluster configuration service is up and running.
> (1) Executing - status locator --name=locator1
> Gfsh must be connected in order to get the status of a Locator by member name or ID.
> (1) Executing - stop locator --dir=/tmp/junit6693528666226757220/locator1
> ...
> :geode-assembly:integrationTest
> :geode-benchmarks:jar
> :geode-benchmarks:javadoc UP-TO-DATE
> :geode-benchmarks:javadocJar
> ```
> It would be better to redirect IO to a logger so that the output is consistent with the output from other tests.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)