Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1991 @1ambda CI is failed only in Selenium test like below ``` Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//i[@tooltip='WebSocket Connected']"} For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html Build info: version: '2.48.2', revision: '41bccdd10cf2c0560f637404c2d96164b67d9d67', time: '2015-10-09 13:08:06' System info: host: 'testing-docker-88bd8952-3a71-4bd6-9ab2-4b1a5ee75b91', ip: '172.17.0.6', os.name: 'Linux', os.arch: 'amd64', os.version: '4.8.12-040812-generic', java.version: '1.7.0_76' Driver info: driver.version: unknown at <anonymous class>.FirefoxDriver.prototype.findElementInternal_(file:///tmp/anonymous5623099368356690573webdriver-profile/extensions/fxdri...@googlecode.com/components/driver-component.js:10659) at <anonymous class>.fxdriver.Timer.prototype.setTimeout/<.notify(file:///tmp/anonymous5623099368356690573webdriver-profile/extensions/fxdri...@googlecode.com/components/driver-component.js:621) Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 75.142 sec <<< FAILURE! - in org.apache.zeppelin.integration.InterpreterIT ``` Seems it's not directly related to this change, but can we retrigger again just to make sure?
--- 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. ---