Skip to content

Run tests against Python 3.7, too #70

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

Merged
merged 5 commits into from
Feb 5, 2019
Merged

Conversation

stasm
Copy link
Contributor

@stasm stasm commented Jul 18, 2018

No description provided.

@stasm stasm requested a review from Pike July 18, 2018 14:45
Copy link
Contributor

@Pike Pike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep sudo off where possible.

https://github.com/Pike/compare-locales/blob/dd90f1b2941b9c774418ece6a4ae9308e1db6176/.travis.yml shows how to do that.

@stasm
Copy link
Contributor Author

stasm commented Aug 7, 2018

Thanks for the pointer. I didn't know it was possible to have different OS setups in .travis.yml. I updated the PR.

@stasm stasm requested a review from Pike August 7, 2018 14:56
.travis.yml Outdated
include:
- python: 2.7
dist: trusty
sudo: false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(passing by, interested question) Do you really need to repeat the sudo: false, when it's declared at the beginning of the file? Logically, only the 3.7 one would need an override

Copy link
Contributor

@Pike Pike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should test on both nightly and 3.7, I think.

Also, with the recent changes to .travis.yml, this needs work?

(Sorry for the lack of response.)

@stasm
Copy link
Contributor Author

stasm commented Jan 28, 2019

Ugh, I don't understand the Travis and Tox combo. I'll be happy to cede this issue to you, @Pike, if you have ideas on how to fix it. I enabled dist: xenial to turn on the support for Python 3.7. I also followed https://docs.travis-ci.com/user/languages/python/#pypy-support and changed pypy and pypy3 to pypy3.5. It looks like the test now fails because of an actual code issue?

@stasm
Copy link
Contributor Author

stasm commented Jan 28, 2019

I also opened #89 to investigate whether we need Tox at all.

Seems that xenial defaults to a buggy version of pypy. Let's try 6.0, which is the latest release.
@Pike
Copy link
Contributor

Pike commented Jan 28, 2019

It looks like the test now fails because of an actual code issue?

Yes, sadly. Filed #90 on that.

@stasm stasm changed the title Run tests against Python 3.7, rather than nightly Run tests against Python 3.7, too Jan 29, 2019
@stasm
Copy link
Contributor Author

stasm commented Jan 29, 2019

Thanks for looking into the pypy issue, @Pike, and for landing the fix directly on my branch.

@stasm stasm mentioned this pull request Jan 29, 2019
@stasm
Copy link
Contributor Author

stasm commented Jan 30, 2019

I merged master (with the fix from #90) into my branch. Travis is green now. @Pike, do we still need to specify pypy3.5-6.0?

@Pike
Copy link
Contributor

Pike commented Jan 30, 2019

do we still need to specify pypy3.5-6.0?

I'd say yes, I think it does two things for us: One, it's getting us the latest release that we'd end up with locally. The other is, it's pinning us to that release, so we're not getting back in the same boat we were in here, that a change of pypy under the hood breaks our tests, w/out actually being attributed to a pypy change.

We should also add back pypy-6.0 in addition to pypy3.5-6.0

@stasm
Copy link
Contributor Author

stasm commented Jan 30, 2019

OK, thanks for the help. I think this is good to land now. It ended up being a very simple PR :)

@stasm stasm merged commit 75a6fd2 into projectfluent:master Feb 5, 2019
@stasm stasm deleted the test-py37 branch February 5, 2019 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants