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

Hadoop QA commented on AMBARI-19270:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844257/AMBARI-19270.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:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> Log successful agent cache update at info level
> -----------------------------------------------
>
>                 Key: AMBARI-19270
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19270
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.5.0
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: AMBARI-19270.patch
>
>
> Currently all agent cache updates are logged only at debug level unless some 
> error happens. Successful downloads should be logged at info level so we can 
> see if and when updates are performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to