geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-4236) ConfigureEvictionThroughGfsh AcceptanceTest fails due to timeout -- Reconsider default timeout for GfshRule
Date Wed, 10 Jan 2018 23:45:02 GMT


ASF GitHub Bot commented on GEODE-4236:

pdxrunner opened a new pull request #1268: GEODE-4236: Increase default timeout for await
   to avoid false failures on slow machines
   Thank you for submitting a contribution to Apache Geode.
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   - [ ] Has your PR been rebased against the latest commit within the target branch (typically
   - [ ] Is your initial contribution a single, squashed commit?
   - [ ] Does `gradlew build` run cleanly?
   - [ ] Have you written or updated unit tests to verify your changes?
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](
   ### Note:
   Please ensure that once the PR is submitted, you check travis-ci for build issues and
   submit an update to your PR as soon as possible. If you need help, please send an
   email to

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> ConfigureEvictionThroughGfsh AcceptanceTest fails due to timeout -- Reconsider default
timeout for GfshRule
> -----------------------------------------------------------------------------------------------------------
>                 Key: GEODE-4236
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Patrick Rhomberg
> {noformat}
> > configureEvictionByEntryCount
>     org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
>         at org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitLoudly(
>         at org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(
>         at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(
>         at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(
>         at
> {noformat}
> Examining the test itself, it seems that the call
> {noformat}
>     GfshExecution execution = GfshScript
>         .of("start locator --name=locator", "start server --name=server",
>             "create region --name=region1 --eviction-action=local-destroy --eviction-entry-count=1000
>             "create region --name=region2 --eviction-action=overflow-to-disk --eviction-entry-count=1000
>             "create region --name=region3 --eviction-action=overflow-to-disk --eviction-entry-count=1000
>             "create region --name=region4 --eviction-action=local-destroy --eviction-entry-count=1000
>             "create region --name=region5 --eviction-action=overflow-to-disk --eviction-entry-count=1000
>         .execute(gfsh);
> {noformat}
> is executing under the default GfshExecution timeout of 2 minutes.  2 might be optimistic
for the creation of two members and five regions, depending on computational resources available.
> The use of the 2 minute timeout may be the result of an unclear testing API, or might
consider prepending a message with the execution's timeout to the gfsh output stream.

This message was sent by Atlassian JIRA

View raw message