ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jun aoki (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-7294) builds.a.o fails due to TestExecuteHadoopResource test failure as a result of PATH added?
Date Mon, 15 Sep 2014 17:37:33 GMT

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

jun aoki resolved AMBARI-7294.
------------------------------
    Resolution: Duplicate

> builds.a.o fails due to TestExecuteHadoopResource test failure as a result of PATH added?
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7294
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7294
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: jun aoki
>            Assignee: jun aoki
>
> We have been experiencing some build error due to TestExecuteHadoopResource test failure.
> https://builds.apache.org/job/Ambari-trunk-Commit/237/console
> https://builds.apache.org/job/Ambari-trunk-Commit/236/console
> (search for "FAIL: test_run_command_list") 
> The log looks like this
> {code}
> ======================================================================
> FAIL: test_run_command_list (TestExecuteHadoopResource.TestExecuteHadoopResource)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
>     return func(*args, **keywargs)
>   File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/resource_management/TestExecuteHadoopResource.py",
line 108, in test_run_command_list
>     {'logoutput': False, 'tries': 1, 'user': 'user', 'try_sleep': 0})
> AssertionError: {'environment': {'PATH': '/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Com
[truncated]... != {'logoutput': False, 'tries': 1, 'user': 'user', 'try_sleep': 0}
> + {'logoutput': False, 'tries': 1, 'try_sleep': 0, 'user': 'user'}
> - {'environment': {'PATH': '/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/contrib/views/node.js/target/bin:/home/hudson/tools/java/latest1.7/bin:/home/jenkins/tools/maven/latest/bin:/home/jenkins/tools/java/latest1.7/bin:/home/jenkins/tools/java/latest1.7/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games'},
> -  'logoutput': False,
> -  'tries': 1,
> -  'try_sleep': 0,
> -  'user': 'user'}
> {code}
> "PATH" was set and it is unexpected according to the test script, though having PATH
maybe the right behavior now.
> PATH seems introduced at this commit 
> https://issues.apache.org/jira/browse/AMBARI-7257
> https://github.com/apache/ambari/commit/7d9feb6afa6cd310fb8b11221ab67f01f048dd38#diff-60c339c4081594d0c7a01255655dc3f1
> "Use Versioned RPMS for HDP 2.2 stack and make it plugabable to be able to reuse the
scripts for HDP 2.*"
> Let me send a patch for the tests to have the right assertion.
> [~dsen], please let me know if I get it right with the change.



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

Mime
View raw message