geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-127) FailWithTimeoutOfWaitForOutputToMatchJUnitTest takes too long to execute
Date Fri, 08 Jan 2016 03:53:39 GMT

     [ https://issues.apache.org/jira/browse/GEODE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anthony Baker updated GEODE-127:
--------------------------------
    Affects Version/s:     (was: 1.0.0-incubating)
                       1.0.0-alpha1

> 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-alpha1
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>             Fix For: 1.0.0-incubating
>
>
> 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)

Mime
View raw message