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 failures with ruby2.5 #55
Comments
Hey @boutil - turns out the tests were broken, but not the source code itself. Changes in ruby 2.4 caused problems in the way certain tests were set up. So, fixed the tests and all is well now. Thanks for pinging. For the record, no new release is going out. But, I am interested in whether there are changes you would like in general to Riot. I joined a startup about 8 years ago and only left as of last December (2017). Didn't really get a chance to work on Ruby stuff while I was there, so didn't devote a lot of energy to Riot. Anyway, if you have any thoughts, please post a feature request. Cheers, |
Thanks a lot! Cheers, Cédric |
Hi,
As mentionned in #54, some tests are failing with ruby 2.5.
The last one is caused to the transition from Fixnum to Integer, but in the three other it seems that the AssertionMacro is recording the call to to_s as a message with ruby2.5. When trying to reproduce in irb, I fail. Can you confirm that the library is working correctly, but the problem is caused by the test itself?
The bug is reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888171
Cheers,
Cédric
The text was updated successfully, but these errors were encountered: