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

Ethan Li updated STORM-3390:
----------------------------
    Fix Version/s:     (was: 2.0.1)
                   2.1.0

> Lock python test dependencies so we don't get accidentally upgraded
> -------------------------------------------------------------------
>
>                 Key: STORM-3390
>                 URL: https://issues.apache.org/jira/browse/STORM-3390
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Tests are currently failing on Travis with
> {code}
> [INFO] --- exec-maven-plugin:1.6.0:exec (python2.7-test) @ storm-client ---
> Traceback (most recent call last):
>   File "test_storm_cli.py", line 20, in <module>
>     import mock
>   File "/home/travis/.local/lib/python2.7/site-packages/mock/__init__.py", 
> line 2, in <module>
>     import mock.mock as _mock
>   File "/home/travis/.local/lib/python2.7/site-packages/mock/mock.py", line 
> 69, in <module>
>     from six import wraps
> ImportError: cannot import name wraps
> {code}
> This is most likely because we're installing "mock" via pypi during the 
> build, but we're not specifying a version. Since mock just released a new 
> version, we're getting upgraded to that one on Travis.
> I think we don't want this to happen automagically. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to