[ 
https://issues.apache.org/jira/browse/AMBARI-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940971#comment-15940971
 ] 

Hadoop QA commented on AMBARI-20563:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12860407/AMBARI-20563-trunk-v1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11166//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11166//console

This message is automatically generated.

> Zeppelin : livy2 interpreter is not getting created by default
> --------------------------------------------------------------
>
>                 Key: AMBARI-20563
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20563
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: 2.5.1
>            Reporter: Kshitij Badani
>            Assignee: Renjith Kamath
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20563-trunk-v1.patch
>
>
> Whenever Spark2 and Livy2 is installed on the cluster, I can see only Spark2 
> interpreter getting created in Zeppelin and not the Livy2 interpreter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to