You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kenneth Howe (JIRA)" <ji...@apache.org> on 2018/03/28 15:59:00 UTC

[jira] [Comment Edited] (GEODE-4934) CI Failure: GfshScript timing out intermittently waiting for execution to complete

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

Kenneth Howe edited comment on GEODE-4934 at 3/28/18 3:58 PM:
--------------------------------------------------------------

AcceptanceTest run #10 has a failure that's a little different but results in the same error stack trace as shown in the description. 
{code}
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest > destroyIndexIfExists 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.GfshScript.execute(GfshScript.java:105)
        at org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest.destroyIndexIfExists(DestroyIndexIfExistsTest.java:45)
{code}

Underlying cause of all these failures is a BindException on a port while starting either locators or servers.


was (Author: khowe):
AcceptanceTest run #10 has a failure that's a little different but results in the same error stack trace as shown in the description. 
{code}
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest > destroyIndexIfExists 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.GfshScript.execute(GfshScript.java:105)
	
        at org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest.destroyIndexIfExists(DestroyIndexIfExistsTest.java:45)
{code}

Underlying cause of all these failures is a BindException on a port while starting either locators or servers.

> 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
>
> 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)