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

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

Commit 35d123f235f75a6aab298ed2f4dbb8be4c1740da in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=35d123f ]

GEODE-209: fix ProcessStreamReader and delete unnecessary test


> CI failure: 
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-209
>                 URL: https://issues.apache.org/jira/browse/GEODE-209
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating.M1
>            Reporter: Ashvin
>            Assignee: Kirk Lund
>            Priority: Minor
>              Labels: CI, Flaky
>             Fix For: 1.0.0-incubating.M1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
>       at org.junit.Assert.fail(Assert.java:86)
>       at org.junit.Assert.assertTrue(Assert.java:41)
>       at org.junit.Assert.assertFalse(Assert.java:64)
>       at org.junit.Assert.assertFalse(Assert.java:74)
>       at 
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
>       at 
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
>   public void subTearDown() throws Exception {
>     this.process.waitFor();
>     assertFalse(this.process.isAlive());
>   }
> {code}
> Fix to GEODE-127 may have caused this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to