-
Notifications
You must be signed in to change notification settings - Fork 6
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 suite is failing on newer versions of ruby #7
Comments
Hi @miyagawa! I wanted to check in on this again - are you still interested in maintaining this gem? If not, I can fork the gem and close this issue. |
Hi @rmacklin sorry it took this long to reply to you. I personally don't use this gem and am not interested in its feature development. That said, if there's a trivial fix to make this gem compatible to Rack 2.2, or more recent versions of Ruby, i'm happy to apply the fix and release it to Rubygems. I searched for the error message of that CI build and got bblimke/webmock#683 Looks like the fix is to upgrade the webmock dependency? |
I just pushed a few commits that should address the CI issues, and added the matrix for testing on multiple versions of Ruby. Since this is a test suite only fix, I don't think i need to push the new version of the gem. Let me know if you have any other quesitons. |
Awesome, thank you! I can work on a PR to fix the issue with newer versions of rack. |
I've opened #9 to enable this |
Sorry it took me a while, but here is that PR: #10 |
Hi @miyagawa 👋
First of all, thanks for making this gem! I've been using it for a couple years with great success.
Recently I ran into an issue after upgrading rack. Before digging into that issue, I wanted to see if I could run the test suite locally so that I knew I'd be starting from a green build. Unfortunately, it seems that although CI (running ruby 2.2) is currently passing, there is a test that fails when running on ruby >= 2.4 - see https://travis-ci.org/github/miyagawa/rack-vcr/builds/668545594 and #6.
I have a few questions:
Thanks again for your work on this gem and I look forward to hearing from you!
The text was updated successfully, but these errors were encountered: