Github user bzz commented on the issue:

    https://github.com/apache/zeppelin/pull/1170
  
    Thanks @babupe I think we are almost there! Did another pass and add few 
last things above.
    
    One more thing I noticed is - right now this PR fails the project's CI 
build and we heavily rely on this CI automation in the overall progress of the 
project. So we need to make it green again, in order to be able to merge this. 
    
    From [the 
logs](https://s3.amazonaws.com/archive.travis-ci.org/jobs/145380794/log.txt) it 
looks like tests are failing
    
    ```
    [INFO] Zeppelin: BigQuery interpreter ..................... FAILURE [  
2.834 s]
    [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
(default-testCompile) on project zeppelin-bigquery: Compilation failure: 
Compilation failure:
    [ERROR] 
/home/travis/build/apache/zeppelin/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [ERROR] 
/home/travis/build/apache/zeppelin/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [ERROR] -> [Help 1]
    [ERROR] 
    ```
    
    I tried running `mvn test -pl bigquery` on my machine and got 
    ```
    [INFO] -------------------------------------------------------------
    [ERROR] COMPILATION ERROR :
    [INFO] -------------------------------------------------------------
    [ERROR] 
/Users/..../zeppelin-incubator/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [ERROR] 
/Users/..../zeppelin-incubator/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [INFO] 2 errors
    [INFO] -------------------------------------------------------------
    [INFO] 
------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 20.704 s
    [INFO] Finished at: 2016-07-18T11:34:19+09:00
    [INFO] Final Memory: 37M/363M
    [INFO] 
------------------------------------------------------------------------
    [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
(default-testCompile) on project zeppelin-bigquery: Compilation failure: 
Compilation failure:
    [ERROR] 
/Users/..../zeppelin-incubator/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [ERROR] 
/Users/..../zeppelin-incubator/bigquery/src/test/java/org/apache/zeppelin/bigquery/BigQueryInterpreterTest.java:[41,41]
 package com.google.cloud.bigquery.testing does not exist
    [ERROR] -> [Help 1]
    ```
    
    I'm not 100% sure why is that, may be you could point me to the 
documentation on some pre-requests that I'm missing?
    
    But in case some useful tests can not work without external service 
dependency - the simplest way to fix the CI is to:
     - exclude them from the default build and 
     - document the way to run it manually
    
    You can see an example of how the same was recently done for the python 
interpreter in #1164, in particular regarding 
[PythonInterpreterWithPythonInstalledTest](https://github.com/apache/zeppelin/pull/1164/files#diff-177dacc81c4b28b15b73263d3540968cL33)
 and it's excludion in 
[pom.xml](https://github.com/apache/zeppelin/pull/1164/files#diff-db5740cf5cd90cf11935b92eb80d7908R38)


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