Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test with pypy on Travis CI #866

Closed
wants to merge 2 commits into from
Closed

test with pypy on Travis CI #866

wants to merge 2 commits into from

Conversation

@ploxiln
Copy link
Contributor

@ploxiln ploxiln commented Dec 18, 2016

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

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

@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln ploxiln force-pushed the ploxiln:test_pypy branch from 48e37af to 253f307 Dec 18, 2016
@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln ploxiln force-pushed the ploxiln:test_pypy branch from 253f307 to 7635636 Dec 18, 2016
@ploxiln
Copy link
Contributor Author

@ploxiln ploxiln commented Dec 18, 2016

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

@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln ploxiln force-pushed the ploxiln:test_pypy branch from 7635636 to 9b6013f Dec 18, 2016
@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln ploxiln force-pushed the ploxiln:test_pypy branch from 9b6013f to 4616918 Dec 18, 2016
@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln ploxiln force-pushed the ploxiln:test_pypy branch from 4616918 to f035d4c Dec 18, 2016
@coveralls
Copy link

@coveralls coveralls commented Dec 18, 2016

Coverage Status

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

@ploxiln
Copy link
Contributor Author

@ploxiln 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
Copy link
Member

@bitprophet bitprophet commented Dec 19, 2016

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
Copy link
Member

@bitprophet bitprophet commented Dec 19, 2016

Cherry-picked back to 1.17+.

@bitprophet bitprophet mentioned this pull request Dec 19, 2016
@ploxiln ploxiln deleted the ploxiln:test_pypy branch Sep 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants