Skip to content

Test against the released version of Rails 5.2 #1986

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

Closed
wants to merge 1 commit into from

Conversation

mikegee
Copy link

@mikegee mikegee commented Apr 11, 2018

fixes #1985

.travis.yml Outdated
@@ -141,7 +141,7 @@ matrix:
- rvm: 2.4.4
env: RAILS_VERSION='~> 3.1.12'
- rvm: 2.4.4
env: RAILS_VERSION=5.2.0.rc1
env: RAILS_VERSION=5.2.0
Copy link
Member

Choose a reason for hiding this comment

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

Ah hem, this is in the wrong place, it actually prevents 5.2.0 from running on 2.4.4, it should be include with an entry for each version it supports

Copy link
Author

Choose a reason for hiding this comment

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

Indeed this appears to be at end of some exclusions. But, why is it here? I don’t see anything that would test against 5.2 in the first place.

Looks like I should have added entries under the include on line 60.

Copy link
Member

Choose a reason for hiding this comment

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

Yes it's in the wrong place and no one noticed :)

@mikegee
Copy link
Author

mikegee commented Apr 12, 2018

@JonRowe I think Travis is running the expected jobs now. Please have a look.

@JonRowe
Copy link
Member

JonRowe commented Apr 12, 2018

Strictly speaking I think we need to match whats been done for the 4.x series and have a tilde-whack or the stable branch added as well but I'm ok with merging this as is once green.

@mikegee
Copy link
Author

mikegee commented Apr 13, 2018

I'm having a hard time deciphering the build failure. Does that stuff about system tests stop the spec run with a non-zero exit code?

@JonRowe
Copy link
Member

JonRowe commented Apr 15, 2018

Yes it does, I'm not sure why it's being triggered, there must be some setup thats done for 5.1 that isn't working on 5.2 for some reason

@pedrofurtado
Copy link

Any news about this PR?

@fables-tales
Copy link
Member

I'm closing this in favour of #1959. Which is green against rails 5.2.

@mikegee
Copy link
Author

mikegee commented Apr 23, 2018

👍 thanks Sam!

@mikegee mikegee deleted the patch-1 branch April 23, 2018 01:21
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.

Rails 5.2.0 support
4 participants