Re: [CI] second job exceeds travis.org max job time

Nowadays, the second and the third profile takes around 40~45min. Which is very close to limit of travis 50min. I've seen sometimes second or the third profile just fails because of it takes longer than usual (by slow network download, etc). I think we need to split second/third profile so the

Re: [CI] second job exceeds travis.org max job time

I found same issue. In my case, Zeppelin server won't run. I'm not sure why it happens. On Sat, Mar 18, 2017 at 2:17 AM, Remy Gayet wrote: > nevermind. One of my test is hanging because of a bug somewhere in my code. > > On Fri, Mar 17, 2017 at 12:15 PM, Remy Gayet

Re: [CI] second job exceeds travis.org max job time

nevermind. One of my test is hanging because of a bug somewhere in my code. On Fri, Mar 17, 2017 at 12:15 PM, Remy Gayet wrote: > Hello guys, > > the second build configuration (env below) is now taking too much time ( > > 49min) and gets killed, as per travis.org policy (

[CI] second job exceeds travis.org max job time

Hello guys, the second build configuration (env below) is now taking too much time ( > 49min) and gets killed, as per travis.org policy ( https://docs.travis-ci.com/user/customizing-the-build#Build-Timeouts). SCALA_VER=\"2.11\" SPARK_VER=\"2.1.0\" HADOOP_VER=\"2.6\" LIVY_VER=\"0.3.0\"