You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2016/12/13 01:44:58 UTC

[jira] [Commented] (GEODE-209) CI failure: FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch

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

Kirk Lund commented on GEODE-209:
---------------------------------

There's a race condition between {code}this.process.destroy();{code} and the ProcessStreamReader.

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