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

2018-07-24 Thread Jinmei Liao (JIRA) 


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

Jinmei Liao updated GEODE-4934:
---
Labels: CI pull-request-available swat  (was: CI pull-request-available)

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

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

2018-03-29 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot updated GEODE-4934:
--
Labels: CI pull-request-available  (was: CI)

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

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

2018-03-28 Thread Kenneth Howe (JIRA) 

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

Kenneth Howe updated GEODE-4934:

Summary: CI Failure: GfshScript timing out intermittently waiting for 
execution to complete  (was: CI Failure: GfshScript timing out intermittently 
wiating ofr execution to complete)

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