You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/07/29 18:34:05 UTC
[jira] [Commented] (GEODE-127)
FailWithTimeoutOfWaitForOutputToMatchJUnitTest takes too long to execute
[ https://issues.apache.org/jira/browse/GEODE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646362#comment-14646362 ]
ASF subversion and git services commented on GEODE-127:
-------------------------------------------------------
Commit 94939c1f9cc3e09c4beee1155404dd82b9aca13f in incubator-geode's branch refs/heads/develop from [~apache@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=94939c1 ]
GEODE-127: Improve test reliability and execution speed.
Recategorize tests involving spawned processes and file system I/O as
IntegrationTests.
Improve reliability and shorten execution time. Fix up asynchronous waits,
correct JUnit 4 syntax and misc code tidying.
Add new TestSuite classes for targeted testing of test.golden and
test.process packages.
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest takes too long to execute
> ------------------------------------------------------------------------
>
> Key: GEODE-127
> URL: https://issues.apache.org/jira/browse/GEODE-127
> Project: Geode
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Kirk Lund
> Assignee: Kirk Lund
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest takes 303.209 seconds to execute on my laptop. This should be shortened by lowering the timeout in the test.
> The other tests in com.gemstone.gemfire.test.golden take 3+ seconds to execute. Most of the tests in this package are launching for purposes of comparing process output to golden files. They should probably be IntegrationTests instead of UnitTests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)