I also just noticed it today. We used to work with the 120 minutes limit and the builds took way longer as you said. I don't know what's going on here...
It might be related to some issues they reported a few hours ago (https://twitter.com/traviscistatus), but I can't tell. I really hope that the new env is temporary (although the reduced build time is indeed nice ;)). Let's monitor this... – Ufuk On 10 November 2016 at 22:15:51, Greg Hogan (c...@greghogan.com) wrote: > We're getting the dreaded "The job exceeded the maximum time limit for > jobs, and has been terminated." error for some recent Travis-CI builds. > https://travis-ci.org/apache/flink/builds/174615801 > > The docs state that termination will occur when "A job takes longer than 50 > minutes on travis-ci.org", which applies to Flink as well as user GitHub > accounts. > https://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts > > The jobs are running much faster now, as our builds have consistently taken > over an hour and up to an hour and a half. The following recently > successful build looks to be a mix of fast and slow jobs. > https://travis-ci.org/apache/flink/builds/174596630 > > Greg >
