[stormbrew]

Honestly, just the fact that rubyspec exposes a segfault in a new release is more than reason enough that they should be using it. It is de facto a more complete test suite than the ad hoc one they've been making.

Given that, the onus is on the MRI developers to demonstrate why they are actively avoiding the use of a tool that could improve the stability of their language and environment.

[headius]

They have used and contributed to RubySpec in the past, but many (like me) were turned off by the maintainers' attitudes toward contributors and lack of respect. For example, see the zenspider link elsewhere in this thread.

Nobody questions RubySpec as a project. But there are many nontechnical reasons why it was never adopted wholeheartedly by ruby-core.

[joevandyk]

Now that the main maintainer quit, can those nontechnical reasons be resolved?

[jpgvm]

Hopefully. I would be willing to take a crack at it.

[vidarh]

If you (or anyone else) do, I'd be ready to help.

[mnarayan01]

> It is de facto a more complete test suite than the ad hoc one they've been making.

This is a _huge_ stretch. It's hardly surprising that the suite of tests MRI is running against aren't failing against a _released_ version.