nmatrix icon indicating copy to clipboard operation
nmatrix copied to clipboard

Add Ruby 2.5 and 2.6 to travis configuration

Open translunar opened this issue 6 years ago • 7 comments

From #617 it came to our attention that our Travis configuration is a bit out-of-date.

#610 is slightly different — this is correcting the existing configuration, which still needs to be done. But this issue, here, is just about adding 2.5 and 2.6 to the existing broken configuration.

translunar avatar Apr 09 '18 14:04 translunar

Hey @mohawkjohn, is this issue still up for grabs? I'd like to make a PR.

ngetahun avatar Jul 19 '18 22:07 ngetahun

Yes, please! The Travis configuration is a mess. Take a swing!

translunar avatar Jul 19 '18 22:07 translunar

@ngetahun Did you end up having any luck?

translunar avatar Sep 06 '18 15:09 translunar

Hey there! It looks like this issue has been sitting for a few months—mind if I give it a go?

leesharma avatar Oct 01 '18 21:10 leesharma

By all means!

On Mon, Oct 1, 2018 at 2:11 PM Lee Sharma [email protected] wrote:

Hey there! It looks like this issue has been sitting for a few months—mind if I give it a go?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SciRuby/nmatrix/issues/619#issuecomment-426064409, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKFpKnLevbEq1tZDZmFtD2lO7D0Sw5oks5ugoUIgaJpZM4TMqRI .

translunar avatar Oct 01 '18 23:10 translunar

It looks like there's a compatibility issue between packable and ruby versions ≥ 2.5 (see SciRuby/packable#4). Because of this, tests that use their monkey-patched methods fail in CI for 2.5.1 and 2.6.0-preview2 (an example failure with the same error).

From the discussion on that issue, it looks like the problem isn't going to be resolved anytime soon. Luckily, the tests pass locally for me on OS X and Ubuntu; it looks like the problem is limited to CI and Debian systems. I think your options are:

  • Switch to a different library for packing/unpacking binary data,
  • Disable the broken functionality/tests on incompatible versions/systems, or
  • Delay this issue until they release a patched version.

How do you want to handle this?

leesharma avatar Oct 02 '18 17:10 leesharma

I'd say mark as pending on affected systems. It's difficult to extricate packable, but it's really only used in the Matlab IO, which should eventually become a plugin.

translunar avatar Oct 03 '18 15:10 translunar