[
https://issues.apache.org/jira/browse/PROTON-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123999#comment-17123999
]
Robbie Gemmell edited comment on PROTON-2235 at 6/2/20, 4:19 PM:
-----------------------------------------------------------------
I pointed out the same a while back for Dispatch. Some changes were made in
DISPATCH-1359, and more sincein at least
[https://github.com/apache/qpid-dispatch/commit/79636b02428eeeb7aa74e4f9d96600abf1fbccfb].
These dont entirely do what I originally envisaged [1], as that seems to be
hard to do with cmake/ctests, and so instead sets a lower test class timeout.
Currently defaulting to 600 seconds, so again may not stop Travis timing out
since thats also its timeout and it only applies to each test class.
[1] Something along the lines of what we do with JUnit tests, with every test
method running stuff having its own timeout based around what its doing, e.g
5-10 sec for faster/simpler tests, 20+ for
slower/more-complicated/more-variable ones having more potential points for
delay on a crappy CI systems).
was (Author: gemmellr):
I pointed out the same a while back for DISPATCH. Some changes were made in
DISPATCH-1359, and more sincein at least
https://github.com/apache/qpid-dispatch/commit/79636b02428eeeb7aa74e4f9d96600abf1fbccfb.
These dont entirely do what I originally envisaged \[1\], as that seems to be
hard to do with cmake/ctests, and so instead sets a lower test class timeout.
Currently defaulting to 600 seconds, so again may not stop Travis timing out
since thats also its timeout and it only applies to each test class.
\[1\] Something along the lines of what we do with JUnit tests, with every test
method running stuff having its own timeout based around what its doing, e.g
5-10 sec for faster/simpler tests, 20+ for
slower/more-complicated/more-variable ones having more potential points for
delay on a crappy CI systems).
> 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]
