ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18845) TestHeartbeatHandler.testRegistrationRecoveryConfig is Flaky
Date Thu, 10 Nov 2016 14:08:58 GMT


Hadoop QA commented on AMBARI-18845:

{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:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {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.

> TestHeartbeatHandler.testRegistrationRecoveryConfig is Flaky
> ------------------------------------------------------------
>                 Key: AMBARI-18845
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.5.0
>         Attachments: AMBARI-18845.patch
> {{testRegistrationRecoveryConfig}} seems to fail randomly. We should investigate why
it randomly fails and either try to fix it or mark as an {{@Flaky}} test.
> {code}
> java.lang.AssertionError
> 	at org.apache.ambari.server.agent.TestHeartbeatHandler.testRegistrationRecoveryConfig(
> {code}

This message was sent by Atlassian JIRA

View raw message