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
Run 2.7 tests once #539
Run 2.7 tests once #539
Conversation
974abf8
to
f8585e2
Compare
f8585e2
to
96b42ea
Compare
Why the jruby tests are failing is most probably something unrelated to this change. |
#538 is trying to fix this, feel free to include some of it here to expedite |
Oh, did not notice there were things going on related to those. If the jruby tests are broken anyway at the moment, would it be easiest to just have this go into master and into #538 via a rebase, if you see value in this minor change. |
or then the other way around, this can wait for the changes in #538 to hit master. |
If we have your attention, make the minimal changes to fix the build here. |
By "minimal change" i assume you mean dropping the flaky jruby build. That was done just a moment ago. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, add a period in CHANGELOG and I'll merge ;)
e0280c5
to
cc41edd
Compare
Thanks for the contribution! |
Was using this projects Travis CI configuration as a reference on how one could execute the CodeClimate job and noticed that the tests for Ruby 2.7 were executed twice.
This change leaves the responsibility for testing 2.7 to the Danger+CodeClimate job.