Re: Unstable travis CI recently

2017-01-21 Thread moon soo Lee
> > > > > > > > > >How do you guys think of it? > > > > > > > > > >On Thu, Jan 19, 2017 at 1:56 AM, Felix Cheung < > > > felixcheun...@hotmail.com> > > > > >wrote: > > > > > > > >

Re: Unstable travis CI recently

2017-01-20 Thread Jongyoul Lee
> > felixcheun...@hotmail.com> > > > >wrote: > > > > > > > >> I'd agree. Is there a course of actions you can propose? Disable all > > > >>these > > > >> tests is a not a long term solution, right? > > > >>

Re: Unstable travis CI recently

2017-01-18 Thread Jeff Zhang
ere a course of actions you can propose? Disable all > > >>these > > >> tests is a not a long term solution, right? > > >> > > >> > > >> _ > > >> From: Jeff Zhang mailto:zjf...@gmail.com>> &

Re: Unstable travis CI recently

2017-01-18 Thread Jongyoul Lee
> >> I'd agree. Is there a course of actions you can propose? Disable all > >>these > >> tests is a not a long term solution, right? > >> > >> > >> _ > >> From: Jeff Zhang mailto:zjf...@gmail.com>> > >> Sent: Tuesday, January 17, 2017

Re: Unstable travis CI recently

2017-01-18 Thread Jianfeng (Jeff) Zhang
you can propose? Disable all >>these >> tests is a not a long term solution, right? >> >> >> _ >> From: Jeff Zhang mailto:zjf...@gmail.com>> >> Sent: Tuesday, January 17, 2017 6:01 PM >> Subject: Re: Unstable travis CI r

Re: Unstable travis CI recently

2017-01-18 Thread Jongyoul Lee
eff Zhang mailto:zjf...@gmail.com>> > Sent: Tuesday, January 17, 2017 6:01 PM > Subject: Re: Unstable travis CI recently > To: mailto:dev@zeppelin.apache.org>> > > > > Should we disable these flaky test now ? CI seems become more unstable > recently. It is almost usele

Re: Unstable travis CI recently

2017-01-18 Thread Felix Cheung
I'd agree. Is there a course of actions you can propose? Disable all these tests is a not a long term solution, right? _ From: Jeff Zhang mailto:zjf...@gmail.com>> Sent: Tuesday, January 17, 2017 6:01 PM Subject: Re: Unstable travis CI recently To:

Re: Unstable travis CI recently

2017-01-17 Thread Jeff Zhang
Should we disable these flaky test now ? CI seems become more unstable recently. It is almost useless for me, I never see a success CI recently. Here's one screenshot of recent closed PRs. Most of them has CI failure. IMO, this is pretty bad, especially for new contributors. [image: pasted1]

Re: Unstable travis CI recently

2016-12-13 Thread Jun Kim
@Hoon Thanks for your information :-) I should use that next time! 2016년 12월 13일 (화) 오후 8:23, Park Hoon <1am...@gmail.com>님이 작성: > I totally agree with your opinions. I will work on ZEPPELIN-1739, > ZEPPELIN-1749 first i reported before. > > @Jun Kim. So true. We have to wait long time. FYI, we c

Re: Unstable travis CI recently

2016-12-13 Thread Park Hoon
I totally agree with your opinions. I will work on ZEPPELIN-1739, ZEPPELIN-1749 first i reported before. @Jun Kim. So true. We have to wait long time. FYI, we can use our own travis CI containers to test (I recently learned also!) by configuring your-github-id/zeppelin-repo in travis CI Thanks!

Re: Unstable travis CI recently

2016-12-13 Thread Jun Kim
I definitely agree with you! I reopened my PR twice recently to pass CI and it wasn't because of me. CI takes about ~40min for a test, so I had to wait 1h and 20min to write a comment after passing CI T_T And the worst of it is that I don't believe CI's result more and more. 2016년 12월 13일 (화) 오

Unstable travis CI recently

2016-12-13 Thread Jeff Zhang
Hi Folks, As you may notice that our travis CI is not stable recently. There's many flaky test, and it waste every developer's time to figure out whether the failure is due to your PR or flaky test. So I think it is time for us to make the CI stable. Here's tickets for all the flaky test. https://