[
https://issues.apache.org/jira/browse/AMBARI-16839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298136#comment-15298136
]
Hadoop QA commented on AMBARI-16839:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12805853/AMBARI-16839.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 4 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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6942//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6942//console
This message is automatically generated.
> Need ability to ignoreBadMounts on a large cluster with bad disks vs
> workaround of tens of Config Groups
> --------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16839
> URL: https://issues.apache.org/jira/browse/AMBARI-16839
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16839.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
