[
https://issues.apache.org/jira/browse/AMBARI-18704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608974#comment-15608974
]
Hadoop QA commented on AMBARI-18704:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12835377/AMBARI-18704.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/9002//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9002//console
This message is automatically generated.
> Add code to improve debugging of ambari-agent related problems.
> ---------------------------------------------------------------
>
> Key: AMBARI-18704
> URL: https://issues.apache.org/jira/browse/AMBARI-18704
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18704.patch
>
>
> This is necessary to debug issues on agent level. Where logs doesn't give
> enough insight.
> The commit will include:
> * possibility to debug second agent process without restarting agent
> * show stack traces of where the process threads are without installing any
> additional modules as a separate commit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
