GitHub user soralee opened a pull request:

    https://github.com/apache/zeppelin/pull/1806

    [ZEPPELIN-1863] Travis Selenium CI fail

    ### What is this PR for?
    Currently, the Selenium CI test of Travis regarding every PR is failing. 
    I think because it is after merging #1777 PR. 
    
    Here is error log.
    ```
    Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate 
element: 
{"method":"xpath","selector":"(//div[@ng-controller=\"ParagraphCtrl\"])[2]//div[@class=\"control
 ng-scope\"]//ul[@class=\"dropdown-menu\"]/li[1]"}
    
    
    Results :
    Tests in error: 
      ZeppelinIT.testAngularRunParagraph:291 » NoSuchElement Unable to locate 
elemen...
    ```
    
    ### What type of PR is it?
    [Bug Fix | Hot Fix]
    
    ### Todos
    * [ ] fix code regarding this problem  ( I think there will be another 
problem except this error. )
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1863
    
    ### How should this be tested?
    - None
    
    ### Screenshots (if appropriate)
    - None
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/soralee/zeppelin ZEPPELIN-1863

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1806.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1806
    
----
commit b7a8c0797f364a96bfe802e1bfe2fc11a3c5892d
Author: soralee <sora0...@nflabs.com>
Date:   2016-12-27T07:42:20Z

    travis CI fail for ZeppelinIT.testAngularRunParagraph:291

----


---
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.
---

Reply via email to