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! On Tue, Dec 13, 2016 at 8:19 PM, Jun Kim <i2r....@gmail.com> wrote: > 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일 (화) 오후 8:10, Jeff Zhang <zjf...@gmail.com>님이 작성: > > > 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://issues.apache.org/jira/issues/?jql=project%20% > 3D%20ZEPPELIN%20AND%20text%20~%20flaky%20and%20status%20!% > 3D%20RESOLVED%20ORDER%20%20BY%20status%20ASC%20 > > > > Fixing the flaky test may take some time and may not easy for some test > but > > I think it is worth to do that. And it is better for these people who > > familiar with that particular test case to fix it. What do you guys > think ? > > Thanks > > > -- > Taejun Kim > > Data Mining Lab. > School of Electrical and Computer Engineering > University of Seoul >
