How to increase Travis CI time limit

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

How to increase Travis CI time limit

Jark Wu
Hi devs,

I used to check whether a PR can be merged by using Travis CI on my own
repo branch. But recently I find it doesn't work. Such as this branch [1] ,
 Travis CI failed when reached 50 minutes limit. I find that flink repo can
run more than 1 hr 30 min. Do you know how to increase the time limit of
Travis for my repo?   Or how do you check a PR can be merged currently?

[1] https://travis-ci.org/wuchong/flink/builds/242259542


Thanks,
Jark Wu
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Chesnay Schepler-3
Hello,

there currently isn't a good workaround for contributors.

I'm currently reaching out to Travis support as to whether something
about their infrastructure was changed recently.
It seems unlikely that we didn't notice a commit that adds 50 minutes to
the build times.

Regards,
Chesnay

On 13.06.2017 16:56, Jark Wu wrote:

> Hi devs,
>
> I used to check whether a PR can be merged by using Travis CI on my own
> repo branch. But recently I find it doesn't work. Such as this branch [1] ,
>   Travis CI failed when reached 50 minutes limit. I find that flink repo can
> run more than 1 hr 30 min. Do you know how to increase the time limit of
> Travis for my repo?   Or how do you check a PR can be merged currently?
>
> [1] https://travis-ci.org/wuchong/flink/builds/242259542
>
>
> Thanks,
> Jark Wu
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Robert Metzger
Hi Chesnay,
Thanks a lot for taking care of the issue!
Did you get any insights by talking to the travis support about this?

On Tue, Jun 13, 2017 at 5:07 PM, Chesnay Schepler <[hidden email]>
wrote:

> Hello,
>
> there currently isn't a good workaround for contributors.
>
> I'm currently reaching out to Travis support as to whether something about
> their infrastructure was changed recently.
> It seems unlikely that we didn't notice a commit that adds 50 minutes to
> the build times.
>
> Regards,
> Chesnay
>
>
> On 13.06.2017 16:56, Jark Wu wrote:
>
>> Hi devs,
>>
>> I used to check whether a PR can be merged by using Travis CI on my own
>> repo branch. But recently I find it doesn't work. Such as this branch [1]
>> ,
>>   Travis CI failed when reached 50 minutes limit. I find that flink repo
>> can
>> run more than 1 hr 30 min. Do you know how to increase the time limit of
>> Travis for my repo?   Or how do you check a PR can be merged currently?
>>
>> [1] https://travis-ci.org/wuchong/flink/builds/242259542
>>
>>
>> Thanks,
>> Jark Wu
>>
>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Chesnay Schepler-3
Last week they suggested to use a sudo-enabled environment (by modifying
our travis.yml)
as they have more memory available. This should only buy us a few
minutes though.

I haven't heard from them since, and they never provided an explanation
for increased
build times. According to them nothing changed on their side.

It is not a problem on our side though, that's a fact by now. Branches
that haven't been
modified, like the release-1.2 branch, now also time out.

That said, if both travis and we haven't changed anything, maybe
Apache/Infra had
anything to do with it?

On 22.06.2017 12:12, Robert Metzger wrote:

> Hi Chesnay,
> Thanks a lot for taking care of the issue!
> Did you get any insights by talking to the travis support about this?
>
> On Tue, Jun 13, 2017 at 5:07 PM, Chesnay Schepler <[hidden email]>
> wrote:
>
>> Hello,
>>
>> there currently isn't a good workaround for contributors.
>>
>> I'm currently reaching out to Travis support as to whether something about
>> their infrastructure was changed recently.
>> It seems unlikely that we didn't notice a commit that adds 50 minutes to
>> the build times.
>>
>> Regards,
>> Chesnay
>>
>>
>> On 13.06.2017 16:56, Jark Wu wrote:
>>
>>> Hi devs,
>>>
>>> I used to check whether a PR can be merged by using Travis CI on my own
>>> repo branch. But recently I find it doesn't work. Such as this branch [1]
>>> ,
>>>    Travis CI failed when reached 50 minutes limit. I find that flink repo
>>> can
>>> run more than 1 hr 30 min. Do you know how to increase the time limit of
>>> Travis for my repo?   Or how do you check a PR can be merged currently?
>>>
>>> [1] https://travis-ci.org/wuchong/flink/builds/242259542
>>>
>>>
>>> Thanks,
>>> Jark Wu
>>>
>>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Robert Metzger
I wonder how ASF Infra can influence our builds times at Travis. Afaik
there are no "secret settings" that they can change.

On Thu, Jun 22, 2017 at 12:27 PM, Chesnay Schepler <[hidden email]>
wrote:

> Last week they suggested to use a sudo-enabled environment (by modifying
> our travis.yml)
> as they have more memory available. This should only buy us a few minutes
> though.
>
> I haven't heard from them since, and they never provided an explanation
> for increased
> build times. According to them nothing changed on their side.
>
> It is not a problem on our side though, that's a fact by now. Branches
> that haven't been
> modified, like the release-1.2 branch, now also time out.
>
> That said, if both travis and we haven't changed anything, maybe
> Apache/Infra had
> anything to do with it?
>
>
> On 22.06.2017 12:12, Robert Metzger wrote:
>
>> Hi Chesnay,
>> Thanks a lot for taking care of the issue!
>> Did you get any insights by talking to the travis support about this?
>>
>> On Tue, Jun 13, 2017 at 5:07 PM, Chesnay Schepler <[hidden email]>
>> wrote:
>>
>> Hello,
>>>
>>> there currently isn't a good workaround for contributors.
>>>
>>> I'm currently reaching out to Travis support as to whether something
>>> about
>>> their infrastructure was changed recently.
>>> It seems unlikely that we didn't notice a commit that adds 50 minutes to
>>> the build times.
>>>
>>> Regards,
>>> Chesnay
>>>
>>>
>>> On 13.06.2017 16:56, Jark Wu wrote:
>>>
>>> Hi devs,
>>>>
>>>> I used to check whether a PR can be merged by using Travis CI on my own
>>>> repo branch. But recently I find it doesn't work. Such as this branch
>>>> [1]
>>>> ,
>>>>    Travis CI failed when reached 50 minutes limit. I find that flink
>>>> repo
>>>> can
>>>> run more than 1 hr 30 min. Do you know how to increase the time limit of
>>>> Travis for my repo?   Or how do you check a PR can be merged currently?
>>>>
>>>> [1] https://travis-ci.org/wuchong/flink/builds/242259542
>>>>
>>>>
>>>> Thanks,
>>>> Jark Wu
>>>>
>>>>
>>>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Chesnay Schepler-3
I would be surprised to. I'm only mentioning it since they were able to  
prevent
Flink from hogging all the workers.

On 22.06.2017 12:34, Robert Metzger wrote:

> I wonder how ASF Infra can influence our builds times at Travis. Afaik
> there are no "secret settings" that they can change.
>
> On Thu, Jun 22, 2017 at 12:27 PM, Chesnay Schepler <[hidden email]>
> wrote:
>
>> Last week they suggested to use a sudo-enabled environment (by modifying
>> our travis.yml)
>> as they have more memory available. This should only buy us a few minutes
>> though.
>>
>> I haven't heard from them since, and they never provided an explanation
>> for increased
>> build times. According to them nothing changed on their side.
>>
>> It is not a problem on our side though, that's a fact by now. Branches
>> that haven't been
>> modified, like the release-1.2 branch, now also time out.
>>
>> That said, if both travis and we haven't changed anything, maybe
>> Apache/Infra had
>> anything to do with it?
>>
>>
>> On 22.06.2017 12:12, Robert Metzger wrote:
>>
>>> Hi Chesnay,
>>> Thanks a lot for taking care of the issue!
>>> Did you get any insights by talking to the travis support about this?
>>>
>>> On Tue, Jun 13, 2017 at 5:07 PM, Chesnay Schepler <[hidden email]>
>>> wrote:
>>>
>>> Hello,
>>>> there currently isn't a good workaround for contributors.
>>>>
>>>> I'm currently reaching out to Travis support as to whether something
>>>> about
>>>> their infrastructure was changed recently.
>>>> It seems unlikely that we didn't notice a commit that adds 50 minutes to
>>>> the build times.
>>>>
>>>> Regards,
>>>> Chesnay
>>>>
>>>>
>>>> On 13.06.2017 16:56, Jark Wu wrote:
>>>>
>>>> Hi devs,
>>>>> I used to check whether a PR can be merged by using Travis CI on my own
>>>>> repo branch. But recently I find it doesn't work. Such as this branch
>>>>> [1]
>>>>> ,
>>>>>     Travis CI failed when reached 50 minutes limit. I find that flink
>>>>> repo
>>>>> can
>>>>> run more than 1 hr 30 min. Do you know how to increase the time limit of
>>>>> Travis for my repo?   Or how do you check a PR can be merged currently?
>>>>>
>>>>> [1] https://travis-ci.org/wuchong/flink/builds/242259542
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Jark Wu
>>>>>
>>>>>
>>>>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Robert Metzger
They talked to Travis to limit the worker allocation per project (I think
they've mentioned this in one of the INFRA JIRAs).

Did you try out the sudo enabled environment? Maybe this is saving us a few
minutes. But one of the issues was also vastly different build times on the
same commit. Maybe this infra is more consistent with the runtimes?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to increase Travis CI time limit

Chesnay Schepler-3
I only ran it on a branch limited to 50 minutes; based on my
calculations it saved us 5 minutes,
but i can open a PR to try it out for a full build.

On 22.06.2017 15:37, Robert Metzger wrote:
> They talked to Travis to limit the worker allocation per project (I think
> they've mentioned this in one of the INFRA JIRAs).
>
> Did you try out the sudo enabled environment? Maybe this is saving us a few
> minutes. But one of the issues was also vastly different build times on the
> same commit. Maybe this infra is more consistent with the runtimes?
>

Loading...