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

Jaimin D Jetly commented on AMBARI-13439:
-----------------------------------------

[~nalex]

I applied the patch and ran ambari-server python unit test in my local dev 
environment (Mac) but there are 13 failures with the patch. All failures seems 
to be because of same reason as it has same error trace
{code}
Traceback (most recent call last):
  File 
"/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/ambari/ambari-server/../ambari-common/src/test/python/mock/mock.py",
 line 1191, in patched
    arg = patching.__enter__()
  File 
"/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/ambari/ambari-server/../ambari-common/src/test/python/mock/mock.py",
 line 1250, in __enter__
    self.target = self.getter()
  File 
"/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/ambari/ambari-server/../ambari-common/src/test/python/mock/mock.py",
 line 1412, in <lambda>
    getter = lambda: _importer(target)
  File 
"/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/ambari/ambari-server/../ambari-common/src/test/python/mock/mock.py",
 line 1096, in _importer
    thing = __import__(import_path)
ImportError: No module named hawqstandby
{code}

Please address the issue, rebase and reattach the patch to the Jira, so Hadoop 
QA job runs again.


> Unit tests for the HAWQ service under common-services
> -----------------------------------------------------
>
>                 Key: AMBARI-13439
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13439
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Newton Alex
>            Assignee: Newton Alex
>            Priority: Minor
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13439.patch
>
>
> This is a follow up task to AMBARI-12320. We have to add unit tests for HAWQ 
> service under common-services.



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

Reply via email to