You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/18 01:18:59 UTC
[jira] [Commented] (AMBARI-11200) Fix ignored persistence-related
unit tests
[ https://issues.apache.org/jira/browse/AMBARI-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547382#comment-14547382 ]
Hadoop QA commented on AMBARI-11200:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12733399/AMBARI-11200.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 8 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:
org.apache.ambari.server.state.cluster.ClusterTest
org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest
org.apache.ambari.server.orm.dao.AlertDispatchDAOTest
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2753//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2753//console
This message is automatically generated.
> Fix ignored persistence-related unit tests
> ------------------------------------------
>
> Key: AMBARI-11200
> URL: https://issues.apache.org/jira/browse/AMBARI-11200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-11200.patch
>
>
> Moved out of AMBARI-10818 because a lot of tests is exploiting bug https://github.com/google/guice/issues/739 and are non-trivial to fix
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)