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

Add ruby 2.4 support in travis #205

Merged
merged 4 commits into from
May 9, 2017

Conversation

jrafanie
Copy link
Contributor

@jrafanie jrafanie commented May 8, 2017

Note, we need to update to rails 4.2.8 or higher for ruby 2.4 support

See: rails/rails#27473

@jrafanie jrafanie changed the title Add ruby 2.4 support in travis. Add ruby 2.4 support in travis (also upgrade json dev/test dependency) May 8, 2017
@grosser
Copy link
Owner

grosser commented May 8, 2017

thx, try a bundle update to get travis green :)

@jrafanie jrafanie changed the title Add ruby 2.4 support in travis (also upgrade json dev/test dependency) Add ruby 2.4 support in travis May 8, 2017
@jrafanie
Copy link
Contributor Author

jrafanie commented May 8, 2017

This configuration works on ruby 1.9.3 and 2.4.1 locally... here's hoping it works on travis.

I was wrong. I can't get this to pass on 2.4.1 locally.

@grosser
Copy link
Owner

grosser commented May 8, 2017

maybe simplest to do bundle update

- diff-lcs fix upgrade fixes ruby 2.4 deprecations
-  Upgrade rspec and rspec-rerun
Prior to this version, ruby 2.4.1 would get the following error on 4
tests:

`SQLite3::SQLException: cannot rollback - no transaction is active: rollback transaction (ActiveRecord::StatementInvalid)`
@jrafanie
Copy link
Contributor Author

jrafanie commented May 9, 2017

Yes, @grosser, I did that. Although, this seems like an actual issue with 2.4. I'm still tracking it down. Do you have any suggestions?

@grosser
Copy link
Owner

grosser commented May 9, 2017

Nah ... might be sqlite being incompatible ... see if there is anything obvious wrong with the testcase setup / if it works when run with just ruby ... otherwise skip them on 2.4 ... it's not parallels job to fix sqlite ...

@Fryguy
Copy link

Fryguy commented May 9, 2017

Note, we need to update to rails 4.2.8 or higher for ruby 2.4 support

As an aside, since Rails 5.1 is now out, technically Rails 4.2 has gone into security only mode with Rails 5.0 and 5.1 being the supported versions.

@jrafanie
Copy link
Contributor Author

jrafanie commented May 9, 2017

@Fryguy We can't upgrade the test environment rails to 5 since it requires ruby 2.2 or higher I think and parallel is tested all the way back to ruby 1.9.3

@grosser
Copy link
Owner

grosser commented May 9, 2017

can exclude the unsupported combinations like rails 5.0 + 1.9 from the build matrix

We need this sqlite tempfile to stick around until we're done doing
queries so reference the Tempfile and explicitly close and unlink it
when we're done.

This seems to resolve a test issue on ruby 2.4.1 where queries were
failing in threads or processes with:
`attempt to write a readonly database`
@jrafanie
Copy link
Contributor Author

jrafanie commented May 9, 2017

Ok, @grosser I think I got the sqlite issue under control. See the last commit.

@grosser
Copy link
Owner

grosser commented May 9, 2017

good find!

@grosser grosser merged commit d7322bb into grosser:master May 9, 2017
@grosser
Copy link
Owner

grosser commented May 9, 2017

FYI switched to Templfile.open in d396783

@jrafanie
Copy link
Contributor Author

jrafanie commented May 9, 2017

Looks good @grosser

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