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 build can be finished
in 30 min, which gives enough margin for travis build and adding more tests.

Thanks,
moon

On Fri, Mar 17, 2017 at 11:07 PM Jongyoul Lee <jongy...@gmail.com> wrote:

> 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 <remy.ga...@gmail.com> 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 <remy.ga...@gmail.com>
> wrote:
> >
> > > 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\" PROFILE=\"-Pspark-2.1 -Phadoop-2.6 -Ppyspark -Psparkr
> > -Pscalding -Phelium-dev -Pexamples -Pscala-2.11 -Plivy-0.3\"
> > BUILD_FLAG=\"package -Pbuild-distr -DskipRat\" TEST_FLAG=\"verify
> > -Pusing-packaged-distr -DskipRat\" TEST_PROJECTS=\"\""
> > >
> > > Am I the only one experiencing this? If not, any thought on what to
> > remove
> > > to reduce this build duration?
> > >
> > > Cheers,
> > >
> > > Remy (Remilito)
> > >
> > >
> >
> >
> > --
> > Remy GAYET,
> > +33 6 798 798 62.
> >
>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>

Reply via email to