infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kellen Sunderland (JIRA)" <>
Subject [jira] [Commented] (INFRA-17216) [MXNet] Increase limits for Travis CI
Date Mon, 05 Nov 2018 23:14:00 GMT


Kellen Sunderland commented on INFRA-17216:

I've spoken with customer service at Slack just requesting some general information around
how this could be done.  They indicated they do have a setting for global timeouts, and they
would be fine with changing it for Apache, however I'd worry this is then a global setting
applied to all projects.

> [MXNet] Increase limits for Travis CI
> -------------------------------------
>                 Key: INFRA-17216
>                 URL:
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CI
>            Reporter: Marco de Abreu
>            Priority: Major
> Hello,
> as discussed in HipChat with Daniel Gruno, we would be interested in increasing the limits
for our Travis runs. At the moment, we have 2 CPU cores for a duration of 50 minutes. 
> Our project requires a significant time to compile which we usually keep down with the
usage of ccache. Unfortunately, most backend changes invalidate the cache and lead to the
necessity to recompile almost the entire project. This, in combination with the execution
of our test suite, lets us run into a timeout.
> We would like to explore the following options:
> 1. Increase the number of CPU cores per worker to speed up the compilation jobs
> 2. Increase the timeout for our jobs to allow tests to finish gracefully
> 3. Donate capacity ($ or Mac servers) to balance out the increased workload on the Apache
> Thanks for your assistance.

This message was sent by Atlassian JIRA

View raw message