On Thu, Mar 28, 2019 at 3:57 PM Felix Cheung <felixche...@apache.org> wrote:
> I have LANG=“en_US.UTF-8” > I tried a couple of things finally it passed when I use virtualenv - my > python is Python 3, forcing that to Python 2 passed the test. Hmmm, that tells me that the python 3 path in the fake shell might not be as unicode-safe as it seems, and that this test should also be running against python 3... As a separate issue, things could be enhanced so that they force use of "python2" when running the python 2 tests. But in the spirit of "these are not regressions, just bugs", I'd rather not block the release for that. (I filed a but for the ASCII thing already, I'll file others for the above.) > However, now > another test failed (maybe connection blocked by firewall?) > That seems likely, if you have a local firewall? (8998 is Livy's default port. Or maybe you have something running on that port and the tests should be trying an ephemeral one...) > error_msg = "Connection refused by Responses: POST > http://machine:8998/sessions/ doesn't match Responses Mock" > response = ConnectionError(u"Connection refused by Responses: POST > http://machine:8998/sessions/doesn't match Responses Mock",) > -- Marcelo
