Ruby 2.3.3 released

https://www.ruby-lang.org/en/news/2016/11/21/ruby-2-3-3-released/

by lucascaton • 10 years ago

205 22 10 years ago

Exuma2• 10 years ago

Random question, how is a regression like a 'no method error' possible? Don't the creators of these languages write extremely exhaustive tests? I don't know much about this, just wondering...

igravious• 10 years ago

Looks to be a corner case not covered by existing tests prior to now.

“This release contains a bug fix about Refinements and Module#prepend. The mixture use of Module#refine and Module#prepend to the same Class could cause unexpected NoMethodError. This is a regression on Ruby 2.3.2 released last week. See [Bug #12920] for details.”

Presumably it was discovered in the wild, fixed, test cases written, and that fix was pushed. Time taken: 6 days. https://www.ruby-lang.org/en/news/2016/11/15/ruby-2-3-2-rele...

[Bug #12920] https://bugs.ruby-lang.org/issues/12920

Exuma2• 10 years ago

Ok awesome, thanks for explaining!

chrisseaton3• 10 years ago

It isn't possible to write exhaustive tests - there are an infinite number of possible program states.

Well, finite bound by the width of your pointer type, which doesn't help much.

threatofrain• 10 years ago

Can't some programs be proven to be partially or totally correct?

dkubb2• 10 years ago

There is rubyspec, but it doesn't cover all possible paths, just the ones that the developers deemed important enough to test.

What I am curious to know is _what_ does ruby use besides rubyspec? Do they run tests against the top 100, 1000, etc rubygems before releasing? I know other communities like Rust (and even Perl) do this kind of regression testing. While this won't catch all possible regressions it seems like a reasonable starting point to uncover issues before a release.

chrisseaton3• 10 years ago

Do they run tests against the top 100, 1000, etc rubygems before releasing?

I don't believe they do. They only recently started testing against ruby spec.

I work on an alternative implementation, and we are planning to test against literally all the gems in RubyGems ourselves. We test the top 100 or so at the moment.

riffraff3• 10 years ago

ruby has always had its own set of tests, rubyspec is a very recent development.

znpy• 10 years ago

There has been quite a controversy about rubyspec afaik: the tldr is that the de-facto ruby spec is basically 'whatever piece of software capable of running rails'. This is because the ruby devs change stuff around very often and don't keep an official spec of the language, to the extent that the creator of rubyspec had given up.

This might have changed in the meantime, dunno.

https://github.com/rubinius/rubinius-archive/blob/cf54187d42...

greenail• 10 years ago

Is ruby dead? I would have expected more comments...

mhd• 10 years ago

For a patch release?

xutopia• 10 years ago

It's just a patch release including a fix for a minor edge case.

base• 10 years ago

There was the 2.3.2 release 6 days ago. There is not much to say about this release.

mbreedlove• 10 years ago

The release consists of only 6 commits, 3 of which are merges, 1 is tagging the version, 1 is updating the version.h header.

There's only one actual change, https://github.com/ruby/ruby/commit/a5d754acb8cfd6d3ac9f26b1...

Source: https://github.com/ruby/ruby/compare/v2_3_2...v2_3_3#diff-02...

smnplk• 10 years ago

What is the frequency of new ruby job posts these days, few and far between ?

Ruby 2.3.3 released

Related Stories