[
https://issues.apache.org/jira/browse/AVRO-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989501#comment-16989501
]
Ryan Skraba commented on AVRO-2630:
-----------------------------------
Another idea for a quick win -- I measured some times on a single docker build
in travis:
||Step||Time||
|apt-get|00:01:59|
|nodejs|00:00:24|
|php|00:00:41|
|perl|00:09:28|
|python2|00:00:08|
|python3|00:00:10|
|.NET|00:01:34|
|Ruby|00:00:45|
Setting up *perl* via CPAN is pretty long and disproportionate to the others.
Most (or all?) of the perl modules are available as packages via apt-get
(`apt-get install libperl-critic-perl` instead of `cpanm install Perl::Critic`).
Would there be any objection if I made this modification? I imagine that the
apt packages are updated more slowly than CPAN, but I don't know if it would be
a significant difference to a perl user.
> 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)
