[
https://issues.apache.org/jira/browse/DISPATCH-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864448#comment-16864448
]
ASF subversion and git services commented on DISPATCH-1359:
-----------------------------------------------------------
Commit b172f501028b36d786b4c83bcee1e195cd17fcf2 in qpid-dispatch's branch
refs/heads/master from Charles E. Rolke
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=b172f50 ]
DISPATCH-1359: Change ctest timeout default value
The default timeout is 360 seconds. The previous value of 300 seconds was
too tight on many CI build systems.
A single timeout value in seconds may be specified on the CMake command line:
-DDISPATCH_TEST_TIMEOUT=300
The single default applies to all tests.
> Set ctest timeout to 300 seconds.
> ---------------------------------
>
> Key: DISPATCH-1359
> URL: https://issues.apache.org/jira/browse/DISPATCH-1359
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.7.0
> Reporter: Ganesh Murthy
> Assignee: Chuck Rolke
> Priority: Minor
> Fix For: 1.9.0
>
>
> Currently when running system tests, ctest has a default timeout of 1500
> seconds which is way too long. So for example, system_tests_edge_router if it
> should hang for some reason, gets terminated by ctest only after 1500 seconds
> (25 mins). This is way too long.
> We need to set a smaller more reasonable timeout per test for ctest.
> system_tests_edge_router is the longest executing test in the test suite.
> Looking at how long it takes to execute on a slow Travis system, we have
> reached the conclusion that 300 seconds would be a good timeout value for
> ctest.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
