test with pypy on Travis CI #866

Closed
wants to merge 2 commits into
from

Projects

None yet

3 participants

@ploxiln
Contributor
ploxiln commented Dec 18, 2016

and remove tox config
as suggested in #838 (comment)

(we'll see how it goes ...)

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage remained the same at 74.319% when pulling d3fd8ec on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage decreased (-0.03%) to 74.291% when pulling 48e37af on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage remained the same at 74.319% when pulling 253f307 on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage increased (+0.01%) to 74.333% when pulling 253f307 on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls

Coverage Status

Coverage remained the same at 74.319% when pulling 253f307 on ploxiln:test_pypy into a6b7648 on paramiko:master.

@ploxiln
Contributor
ploxiln commented Dec 18, 2016

still trying to find a version of pypy3 that will work ;)

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage increased (+0.01%) to 74.333% when pulling 7635636 on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage increased (+0.03%) to 74.347% when pulling 9b6013f on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage decreased (-0.01%) to 74.305% when pulling 4616918 on ploxiln:test_pypy into a6b7648 on paramiko:master.

@coveralls
coveralls commented Dec 18, 2016 edited

Coverage Status

Coverage increased (+0.03%) to 74.347% when pulling f035d4c on ploxiln:test_pypy into a6b7648 on paramiko:master.

@ploxiln
Contributor
ploxiln commented Dec 18, 2016

I gave up on finding a new-enough version of pypy3 available on Travis CI. Anyway, this passes tests now with pypy2.7-5.4.1 added to the testing matrix.

@bitprophet
Member

Yup, last time I looked at a PyPy related issue (was only a number of weeks ago, probably over on pyinvoke/invoke), it needed PyPy3+ to truly be considered fixed, and Travis didn't have that yet. So we're kinda waiting on that before we can be super happy.

Sounds like you got tests working on a good-enough PyPy version anyways tho. thanks!

@bitprophet bitprophet added a commit that closed this pull request Dec 19, 2016
@bitprophet bitprophet Changelog closes #866, closes #838 f52a68e
@bitprophet
Member

Cherry-picked back to 1.17+.

@bitprophet bitprophet referenced this pull request Dec 19, 2016
Closed

Fix tests #838

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment