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

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

The test is attempting to wait for the spawned Process to die and this appears 
to take longer on the ASF infrastructure. The assertion was added to prevent 
leaving orphaned processes behind. I hate to change the tests to simply wait 
around indefinitely for the spawned Process to die, so I think the best 
compromise is to remove this assertion since it's not part of the actual test.

> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  is not stable
> ------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-209
>                 URL: https://issues.apache.org/jira/browse/GEODE-209
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Ashvin
>            Assignee: Kirk Lund
>            Priority: Minor
>
> 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