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 l
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
wrote:
> Hello,
>
> there currently isn't a good workaround for contributors.
>
> I'm currently reaching out to Travis su
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 nothi
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
wrote:
> Last week they suggested to use a sudo-enabled environment (by modifying
> our travis.yml)
> as they have more m
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, Ju
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 th
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
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
O
