You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Dale Richardson (Jira)" <ji...@apache.org> on 2020/05/08 07:39:00 UTC

[jira] [Updated] (LIVY-768) Livy Python API tests require dependency version pinning

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

Dale Richardson updated LIVY-768:
---------------------------------
    Issue Type: Bug  (was: Improvement)

> Livy Python API tests require dependency version pinning
> --------------------------------------------------------
>
>                 Key: LIVY-768
>                 URL: https://issues.apache.org/jira/browse/LIVY-768
>             Project: Livy
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.7.0
>            Reporter: Dale Richardson
>            Priority: Minor
>
> Building Livy inside a brand new virtualenv with the latest version of the unpinned dependencies listed in 
> *python-api/setup.py*
> Causes a number of issues that prevents the tests from running cleanly.  Main culprits appear to be pytest (needs to be limited <5) and cloudpickle (needs to be limited to <1.3.0).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)