Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2415
@zjffdu, yeah, I'm also facing tavis failure so many times as well. This is
not a problem that can be fixed with this PR. It's time to that we should take
care of overall selenium test.
here is one thought in my head to quickly resolve issue, how about spliting
the 3rd job in Travis? I guess many people keep failing the 2nd and 3rd jobs,
because it tooks long time than other job.
And then, we can improve overall selenium for avoid flaky test.
what do you think of?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
