[
https://issues.apache.org/jira/browse/PROTON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182114#comment-17182114
]
Charles E. Rolke commented on PROTON-2270:
------------------------------------------
>>> In the CTest world, tests are free to set their own timeouts, overriding
>>> the default, if they "think they know better".
For users without a local build wherein they can edit cmake and rebuild, the
cli switch is the only way to go. It is possible to allow the ctest command
line user set the timeout. For instance, in qpid-dispatch:
{code:java}
> ctest -VV --timeout 1234 -R s_policy$
...
test 24
Start 24: system_tests_policy
24: Test command: /usr/bin/python
"/home/chug/git/qpid-dispatch/build/tests/run.py" "-m" "unittest" "-v"
"system_tests_policy"
24: Test timeout computed to be: 1234
...
{code}
> Threaderciser test does not honor ctest '--timeout' switch
> ----------------------------------------------------------
>
> Key: PROTON-2270
> URL: https://issues.apache.org/jira/browse/PROTON-2270
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
> Affects Versions: proton-c-0.31.0
> Environment: Fedora 31
> Reporter: Charles E. Rolke
> Priority: Major
>
> Command line
> {code:java}
> > ctest -VV --timeout 600 -R threader
> {code}
> runs the test with
> {code:java}
> ...
> Start 7: c-threaderciser
> ...
> 7: Test timeout computed to be: 120
> ...
> {code}
> The test should respect the ctest switch and run for 600 seconds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
