Hi Pranav, are you having troubles compiling apache-lens ? Because that's how it looks like from steps 1-3 that you describe.
Just FYI with Zeppelin - non of the large tests that use Selenium are run on 'mvn package', they are bind to 'mvn integration-test' only, which is called if you do 'mvn install', which is what CI server runs. That being said, please let me know if you still have problems building zeppelin using `mvn package`. On Tue, May 26, 2015 at 9:01 AM, Corneau Damien <[email protected]> wrote: > Hi, > > We have those kind of problems a lot with selenium tests, thats why we tell > people to use the skipTests option. I myself cannot run the test on my mac, > however CI is working well. > > If its only the selenium tests failing, then its okay to do a PR, since we > only have selenium tests to check that the webapplication is started. Also > the CI will run the tests in your PR anyway. > On May 26, 2015 5:10 AM, "Pranav Kumar Agarwal" <[email protected]> > wrote: > > > Hello, > > > > I'm trying to run tests to complete my transaction for ZEPPELIN-61 [Add > > Lens Interpreter] using following steps: > > 1. git clone https://github.com/apache/incubator-lens.git; cd > > incubator-lens > > 2. mvn package -Dspark.version=1.1.0 -Dhadoop.version=2.4.0 -DskipTests > > 3. mvn package > > > > After successfully running the tests in most of the modules, it hangs > > while running tests at zeppelin-server with the following last few > messages: > > > > ...... > > 01:26:17,698 INFO org.eclipse.jetty.server.handler.ContextHandler:843 - > > stopped o.e.j.s.ServletContextHandler{/api,null} > > 01:26:17,698 INFO org.eclipse.jetty.server.handler.ContextHandler:843 - > > stopped o.e.j.s.ServletContextHandler{/,null} > > 01:26:17,759 INFO org.apache.zeppelin.server.ZeppelinServer:119 - Bye > > > > Results : > > > > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 > > > > [INFO] > > [INFO] --- scalatest-maven-plugin:1.0:test (test) @ zeppelin-server --- > > Discovery starting. > > May 26, 2015 1:26:25 AM org.openqa.selenium.safari.SafariDriverServer > start > > INFO: Server started on port 4006 > > May 26, 2015 1:26:25 AM > > org.openqa.selenium.safari.SafariDriverCommandExecutor start > > INFO: Launching Safari > > May 26, 2015 1:26:25 AM > > org.openqa.selenium.safari.SafariDriverCommandExecutor start > > INFO: Waiting for SafariDriver to connect > > May 26, 2015 1:26:31 AM > > org.openqa.selenium.safari.SafariDriverChannelHandler$1 operationComplete > > INFO: Connection opened > > May 26, 2015 1:26:31 AM > > org.openqa.selenium.safari.SafariDriverCommandExecutor start > > INFO: Driver connected in 5991 ms > > Discovery completed in 27 seconds, 242 milliseconds. > > Run starting. Expected test count is: 1 > > Zeppelin start [ OK ] > > > > Any ideas on how to debug this? as the test just hangs after printing the > > above message. > > > > I can see that the firefox is opened, however nothing gets written in the > > address bar. > > In zeppelin-server/target/surefire-reports directory I don't see any > error. > > > > In logs directory I see nothing alarming: > > 01:27:00,295 INFO org.apache.zeppelin.interpreter.InterpreterFactory:190 > > - className = org.apache.zeppelin.markdown.Markdown > > 01:27:00,343 INFO > > org.apache.commons.vfs2.impl.StandardFileSystemManager:138 - Using > > "/var/folders/_2/qrx_czzd3n96xbc4pqk9r3zs8_z3n9/T/vfs_cache" as temporary > > files store. > > 01:27:02,006 INFO org.apache.cxf.endpoint.ServerImpl:94 - Setting the > > server's publish address to be / > > 01:27:03,190 INFO > > org.eclipse.jetty.webapp.StandardDescriptorProcessor:284 - NO JSP Support > > for /, did not find org.apache.jasper.servlet.JspServlet > > May 26, 2015 1:27:03 AM com.sun.jersey.api.core.PackagesResourceConfig > init > > INFO: Scanning for root resource and provider classes in the packages: > > org.apache.zeppelin.rest > > com.wordnik.swagger.jersey.listing > > May 26, 2015 1:27:03 AM com.sun.jersey.api.core.ScanningResourceConfig > > logClasses > > INFO: Root resource classes found: > > class org.apache.zeppelin.rest.ZeppelinRestApi > > class com.wordnik.swagger.jersey.listing.ApiListingResourceJSON > > class org.apache.zeppelin.rest.InterpreterRestApi > > class org.apache.zeppelin.rest.NotebookRestApi > > May 26, 2015 1:27:03 AM com.sun.jersey.api.core.ScanningResourceConfig > > logClasses > > INFO: Provider classes found: > > class com.wordnik.swagger.jersey.listing.JerseyApiDeclarationProvider > > class com.wordnik.swagger.jersey.listing.JerseyResourceListingProvider > > May 26, 2015 1:27:04 AM > > com.sun.jersey.server.impl.application.WebApplicationImpl _initiate > > INFO: Initiating Jersey application, version 'Jersey: 1.9 09/02/2011 > 11:17 > > AM' > > May 26, 2015 1:27:04 AM > > com.sun.jersey.server.impl.application.WebApplicationImpl _initiate > > INFO: Adding the following classes declared in > > META-INF/services/jersey-server-components to the resource configuration: > > class org.atmosphere.jersey.AtmosphereResourceConfigurator > > May 26, 2015 1:27:08 AM com.sun.jersey.spi.inject.Errors > > processErrorMessages > > WARNING: The following warnings have been detected with resource and/or > > provider classes: > > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > > > org.apache.zeppelin.rest.InterpreterRestApi.listInterpreter(java.lang.String), > > should not consume any entity. > > 01:27:09,106 INFO org.eclipse.jetty.server.AbstractConnector:338 - > > Started [email protected]:8080 > > 01:27:09,107 INFO org.apache.zeppelin.server.ZeppelinServer:106 - > Started > > > > > > This is blocking me to create a pull request for Apache Lens interpreter > > as I would like to run the tests before creating the pull request. > > > > Regards, > > -Pranav. > > > -- -- Kind regards, Alexander.
