On May 20, 2011, at 12:28 PM, Nat Brown wrote:
> anybody working on a generic (system-wide or per-user or configurable?) cache
> of arbitrary .rb -> .rbo similar to how rubyinline works, where llvm
> intermediaries being built are automatically cached and invalidated when the
> associated/under
I it appears I spoke to soon in my previous mail. Reverting to Rspec 2.5 got me
to where I could run basic test but now I get sig fault when I try to use an
expectation (should statement.) It even happens with example code I copied from
the rspec 2.5 docs.
Just for grins, I ran rspec own spec
On 2011-05-20, at 3:28 PM, Nat Brown wrote:
> am i understanding the option being described here as manually forcing a
> pre-compile of .rb gems to .rbo cached to the gems directory (with caveats
> like no backtrace, ymmv)?
Almost. You lose backtraces right now, but that is a temporary tradeoff
am i understanding the option being described here as manually forcing a
pre-compile of .rb gems to .rbo cached to the gems directory (with caveats
like no backtrace, ymmv)?
anybody working on a generic (system-wide or per-user or configurable?)
cache of arbitrary .rb -> .rbo similar to how rubyin
Rspec 2.6 works on the macruby nightly builds.
Load times are partly due to rubygems being very slow on MacRuby and rspec
being split into 4 gems (plus one other external gem).
The other problem is that you have to JIT all the code at run time; you should
be able to cut the load time in half by
I have the same (performance) issue too. I believe this is due to MacRuby's
JIT, which compiles the ruby source into machine code using LLVM. This improves
performance dramatically for long-running apps, but in our case it seems to
cause a big up-front penalty.
Does anyone else on list know if
Christian,
Reverting to Rspec 2.5 allowed rspec to run under macruby (so far.) However, it
is extremely slow compared to running under system ruby. it takes 10+ seconds
to run just an empty test and pegs out one of my cores to do so.
Macruby should run faster than the system ruby 1.8.7 so I th
Hey Shannon,
I just ran into this problem myself. I believe it has something to do with
RSpec 2.6, since I don't get the error when rspec 2.5 is installed.
Can you try downgrading and see if that helps you as well?
christian.
On May 19, 2011, at 9:58 AM, Shannon Love wrote:
> I had previously
I had previously had Rspec running under Macruby before I tried to use RVM to
manage my ruby installs. Something went awry with RVM and I had to uninstall.
After that Rspec stopped working under Macruby. I
I found that my RVM had installed Macruby 0.11 dev in or over my 0.10 install
and that re
