ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-15051) Improvements and fixes for database check
Date Tue, 16 Feb 2016 11:35:18 GMT


Hadoop QA commented on AMBARI-15051:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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 patch failed these unit tests in ambari-server:


Test results:
Console output:

This message is automatically generated.

> Improvements and fixes for database check
> -----------------------------------------
>                 Key: AMBARI-15051
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.2.2
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.2
>         Attachments: AMBARI-15051.patch
> – Log outputs to a separate file (this is already an ask from SmartSense)
> – Use ERROR/WARNING/INFO to mark logs that fit the level
> – Either the python script or the system test validation code can parse the log file
for ERROR and WARNING logs and post a summary - as Sunitha Velpula suggested.
> – Take in account fact that clusters count could be more then one in service config

This message was sent by Atlassian JIRA

View raw message