[
https://issues.apache.org/jira/browse/PROTON-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156255#comment-17156255
]
Jiri Daněk commented on PROTON-2235:
------------------------------------
I've put a CTest timeout onto c-threaderciser (because it is needed there, the
test sometimes freezes).
Next step would probably be to add timeouts to the other test targets. I am
worried that since there are no "reasonable" limits that can be set upfront
(because the number of tests inside a test target can change), we will end up
fiddling with the limits... If there are other CTest targets which include only
one test (such as the threaderciser), it makes sense to set limits there. For
the other targets, I am inclined to set a 9 minute default limit, just to
ensure we won't get a travis timeout, and leave it at that.
> CTest timeouts are too large to be useful on Travis CI
> ------------------------------------------------------
>
> Key: PROTON-2235
> URL: https://issues.apache.org/jira/browse/PROTON-2235
> Project: Qpid Proton
> Issue Type: Test
> Affects Versions: proton-c-0.31.0
> Reporter: Jiri Daněk
> Priority: Major
>
> https://travis-ci.org/github/apache/qpid-proton/jobs/693871917
> The timeouts of 1500s are too large and do not step in before Travis timeout
> kills the entire job:
> {noformat}
> 6: Test command: /opt/pyenv/shims/python
> "/home/travis/build/apache/qpid-proton/scripts/env.py" "--"
> "TEST_EXE_PREFIX=/usr/bin/valgrind --tool=memcheck --leak-check=full
> --error-exitcode=42 --quiet
> --suppressions=/home/travis/build/apache/qpid-proton/tests/valgrind.supp"
> "/usr/bin/valgrind" "--tool=memcheck" "--leak-check=full"
> "--error-exitcode=42" "--quiet"
> "--suppressions=/home/travis/build/apache/qpid-proton/tests/valgrind.supp"
> "/home/travis/build/apache/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
