[
https://issues.apache.org/jira/browse/GEODE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631676#comment-14631676
]
ASF subversion and git services commented on GEODE-108:
-------------------------------------------------------
Commit a336e81c2fe7666f8e866d3d22f58adcd4a01c18 in incubator-geode's branch
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=a336e81 ]
GEODE-108: Fix up HAInterestPart*DUnitTests
Reformat, fix timeouts, reduce interval for checking asynchronous
criteria. Move tearDown2 up by setUp. Null out static fields during
closeCache so other dunit JVMs don't leak Cache/DS instances. Remove
sleep call. Add @SuppressWarning and @Override annotations. Use
addExpectedExceptions to fix suspect string failures (including the
one that Jenkins hit). Fix typos.
Add JUnit 4 TestCase for testing these tests together in isolation.
> HAInterestPart2DUnitTest.testInterestRecoveryFailure failed with suspect
> string
> -------------------------------------------------------------------------------
>
> Key: GEODE-108
> URL: https://issues.apache.org/jira/browse/GEODE-108
> Project: Geode
> Issue Type: Bug
> Reporter: Kirk Lund
> Assignee: Kirk Lund
>
> {code}
> com.gemstone.gemfire.internal.cache.tier.sockets.HAInterestPart2DUnitTest >
> testInterestRecoveryFailure FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 3864
> java.net.SocketException: Connection reset by peer
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
