[
https://issues.apache.org/jira/browse/AMBARI-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585395#comment-14585395
]
Hadoop QA commented on AMBARI-11922:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12739540/AMBARI-11922.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
contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3181//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3181//console
This message is automatically generated.
> Be able to determine which build a particular view comes from
> -------------------------------------------------------------
>
> Key: AMBARI-11922
> URL: https://issues.apache.org/jira/browse/AMBARI-11922
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Erik Bergenholtz
> Fix For: 2.1.0
>
> Attachments: AMBARI-11922.patch
>
>
> Currently there is no way to determine which build a particular view is
> derived from. It should be possible to determine this by introspecting the
> views' view.xml file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
