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

Hadoop QA commented on AMBARI-15314:
------------------------------------

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

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

This message is automatically generated.

> [forward port to trunk] Introduce possibility to retry stack installation in 
> case of network instability
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15314
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15314
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Dmytro Grinenko
>            Assignee: Dmitry Lysnichenko
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: AMBARI-15314.patch
>
>
> In case if repository bits transfer errors in environments with unreliable 
> connection, installation of HDP stack need to be able to try download 
> packages again.



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

Reply via email to