After shifting up to 127 I can’t get run the rubyspecs any more.
I fixed up the .irconfig.rb and default.mspec files correctly (by the
way I
had to explicitly specify the MRI binary file in .irconfig.rb since it
didn’t seem to be able to find it any more).
I have also pulled the latest mspec, rubyspec and ironruby-tags from
jflam’s
GitHub account. (I also tried pulling in Jim D.'s versions too).
Now when I run a rubyspec I get:
D:\dev\ruby\ironruby\r127>rake mspec:core Fixnum
(in D:/dev/ruby/ironruby/r127)
d:\dev\ruby\ironruby\r127\src\microsoft.scripting.core\actions\callsite.cs:2
88:in `UpdateAndExecute’: No such file or directory - No such file or
directory - d:/dev/ruby/ironruby/r127/tests/ironruby/u
til/and (Errno::ENOENT)
from
d:\dev\ruby\ironruby\r127\src\microsoft.scripting.core\actions\updatedelegat
es.generated.cs:34:in `Update2’
from
d:\dev\ruby\ironruby\r127\src\microsoft.scripting.core\runtime\ScriptCode.cs
:79:in `Run’
from
d:\dev\ruby\ironruby\r127\src\microsoft.scripting.core\sourceunit.cs:246:in
`ExecuteProgram’
rake aborted!
Command failed with status (1): [d:/ruby/bin/ruby.exe
d:/dev/ruby/ironruby/…]
D:/dev/ruby/ironruby/r127/rakefile:409:in `invoke_mspec’
(See full trace by running task with --trace)
I guess there is something inside Rakefile or nearby that is breaking
this?
Unfortunately I can’t get onto the SVN repository to search the log
history
to see what changed (Bring on Git, I say).
Any ideas?
Cheers
Pete