[ 
https://issues.apache.org/jira/browse/GEODE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421007#comment-16421007
 ] 

ASF subversion and git services commented on GEODE-4934:
--------------------------------------------------------

Commit a4bae5c4e36f7d81fbe72925d0046676a29b45cb in geode's branch 
refs/heads/feature/GEODE-4909 from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a4bae5c ]

GEODE-4934: Throw exception if shutdown fails in GfshRule (#1699)

* GEODE-4934: Throw exception if shutdown fails in GfshRule

The conjecture is that we're missing shutdown problems with a test
that can cause problems in later tests. This change is an attempt
to catch the real error in the sporadic AcceptanceTest failures.

Throw the exception if one or more processes failed the shutdown.


> CI Failure: GfshScript timing out intermittently waiting for execution to 
> complete
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-4934
>                 URL: https://issues.apache.org/jira/browse/GEODE-4934
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>    Affects Versions: 1.5.0
>            Reporter: Kenneth Howe
>            Assignee: Kenneth Howe
>            Priority: Major
>              Labels: CI, pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> GfshScript.awaitIfNecessary native method call to determine if the process 
> executing the script is alive hangs. This is not a hard failure, but it can 
> be reproduced with frequently running selected tests from command line. This 
> following set of tests produces failures when run on a Linux host (tested on 
> CentOS 7).
> {code}
> ./gradlew clean geode-lucene:precheckin --parallel -x rat -x javadoc -x 
> spotlessCheck{code}
> {code}
> {code:title=Typical failure stack}
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest > 
> cannotStopServerByNameWhenNotConnected FAILED
>     org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
>         at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>         at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at 
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)
>         at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)
>         at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:87)
>         at 
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:35)
> {code}
> All failures show the same stack from {{at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to