You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2019/06/14 20:58:01 UTC
[jira] [Reopened] (DISPATCH-1359) Set ctest timeout to 300 seconds.
[ https://issues.apache.org/jira/browse/DISPATCH-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke reopened DISPATCH-1359:
-----------------------------------
Assignee: Chuck Rolke (was: Ganesh Murthy)
The fix so as committed has an issue wherein it nullifies the effect of cmake command line option "-- timeout N" (See note 1). Test developers depend on temporarily overriding the test timeout.
Note 1: The timeout can be changed by running ccmake and editing option DART_TESTING_TIMEOUT. However, if cmake sets the test timeout property then that value cannot be overridden.
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org