You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2019/05/05 12:42:00 UTC

[jira] [Created] (STORM-3390) Lock python test dependencies so we don't get accidentally upgraded

Stig Rohde Døssing created STORM-3390:
-----------------------------------------

             Summary: 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


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.3#76005)