[
https://issues.apache.org/jira/browse/AVRO-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977393#comment-16977393
]
Ryan Skraba commented on AVRO-2630:
-----------------------------------
I did a [quick POC|https://github.com/RyanSkraba/avro/pull/2] on omitting perl
entirely from the JAVA=8 build and omitting C++ from the JAVA=11 build: 35
minutes and 43 minutes respectively. This was messy enough to set up although
somehting similar could buy us some time to make more improvements. I have the
feeling doing it for all languages would be exponentially worse (and still not
fully address the interop tests).
I'm doing a bit of reading on what Yetus offers ... hoping to find some tools
there to help.
> 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)
