You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/01/09 17:25:35 UTC

[jira] [Assigned] (AMBARI-9063) Ambari Builds Succeed With Python Unit Test Failures

     [ https://issues.apache.org/jira/browse/AMBARI-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley reassigned AMBARI-9063:
---------------------------------------

    Assignee: Jonathan Hurley

> Ambari Builds Succeed With Python Unit Test Failures
> ----------------------------------------------------
>
>                 Key: AMBARI-9063
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9063
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> The Ambari builds are succeeding locally and on builds.apache.org even though the trunk currently has failures on python tests. See
> https://builds.apache.org/view/All/job/Ambari-trunk-Commit/1441/consoleFull
> And search for "Total run:570"
> It looks like the root cause of this is that the python test runner is reporting an OK with failures:
> {noformat}
> $ python unitTests.py
> ...
> ----------------------------------------------------------------------
> Total run:569
> Total errors:0
> Total failures:4
> OK
> {noformat}
> The problem is that the python test runner is reporting a success:
> {code}
> tests_status = textRunner.wasSuccessful() and not has_failures
> {code}
> {code}
> print textRunner.wasSuccessful()
> True
> print has_failures
> False
> {code}



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