Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-878 ZeppelinIT.testSparkInterpreterDependencyLoading fails
  3. ZEPPELIN-942

CASE III of ZeppelinIT failure - Configuration page visited, instead of Interpreter

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.6.0
    • None
    • None

    Description

      2 similar failures, when on `ZeppelinIT.testSparkInterpreterDependencyLoading` Interpreter page was not visited (it was Configuration or Main page instead)

      #946 - https://s3.amazonaws.com/archive.travis-ci.org/jobs/134570147/log.txt
      #860 - https://s3.amazonaws.com/archive.travis-ci.org/jobs/134671260/log.txt

      Running org.apache.zeppelin.integration.SparkParagraphIT
      
      	at org.apache.zeppelin.integration.SparkParagraphIT.startUp(SparkParagraphIT.java:47)
      Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"partial link text","selector":"Create new note"}
      
      ...
      Running org.apache.zeppelin.integration.ZeppelinIT
      
      	at org.apache.zeppelin.integration.ZeppelinIT.testSparkInterpreterDependencyLoading(ZeppelinIT.java:243)
      Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//div[@id='spark']//form//button[1]"}
      

      From the screenshot - it looks like test ends up on Configuration page, instead of Interpreter page

      Attachments

        1. screenshot-946.png
          53 kB
          Alexander Bezzubov
        2. screenshot-1.png
          45 kB
          Alexander Bezzubov

        Issue Links

          Activity

            People

              prabhjyotsingh Prabhjyot Singh
              bzz Alexander Bezzubov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: