[
https://issues.apache.org/jira/browse/AVRO-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977983#comment-16977983
]
Michael A. Smith commented on AVRO-2630:
----------------------------------------
I think another thing that might help is making the interop tests themselves
faster. Looking at test_rpc_interop.sh, I noticed that it iterates over every
combination of language pairs (and rpc messages and functions), and starts a
new server for every combination. It then waits for that server to come up,
which never takes less than a second. It probably ought to recycle the running
servers when it can. I believe this will shave a significant amount of time off
this test.
real 1m4.829s
...however, things are never simple, and I notice that the python servers exit
as soon as they've fulfilled one request, so that would need to get fixed first.
> Travis build is nearing timeout limits.
> ---------------------------------------
>
> Key: AVRO-2630
> URL: https://issues.apache.org/jira/browse/AVRO-2630
> Project: Apache Avro
> Issue Type: Improvement
> Components: build
> Reporter: Ryan Skraba
> Priority: Major
>
> Single "jobs" on travis are [limited to 50
> minutes|https://docs.travis-ci.com/user/customizing-the-build/#build-timeouts].
> A "normal" build takes 47-48 minutes and can occasionally bump over the
> limit, causing timeout errors.
> We can see that this happens occasionally on master and on pull requests.
> We should find a strategy to limit the length of time for a of the jobs being
> run.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
