y be if it doesn't make sense. Or RubySpec guys if the MRI
behavior is reasonable.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Orion Edwards
Sent: Monday, October 31, 2011 4:40 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-
IronRuby.dll. We'd have to move the Errno stuff out
of Libraries and into IronRuby.dll I think
From: Tomas Matousek
To: "ironruby-core@rubyforge.org"
Date: 01/11/2011 10:16 a.m.
Subject:Re: [Ironruby-core] RubySpecs
Sent by:ironruby-core-boun...@rubyforg
omas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Orion Edwards
Sent: Monday, October 31, 2011 1:19 PM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] RubySpecs
I've just run mspec under the Languages\Ruby\Tests\mspec\rubys
I've just run mspec under the Languages\Ruby\Tests\mspec\rubyspec\core
folder against MRI 1.9.2p0 (which is checked into the ironlanguages-main
git repo), and it crashes with a segfault in putc_spec.rb
I then tried running against MRI 1.9.2p290 and I get the following:
1518 files, 9618 e