Clarification: we've had the means to run RubySpec for a while, and with the exception of coverage numbers, things were fine. We ran into a problem where IronRuby wouldn't respect the exit code you told it to, and that has made us re-evaluate where the specs should be. We are moving them to a git repo like John said. In addition to cleaning out our repo, it will make merging changes to and from RubySpec easier down the road.
Once these changes are finished, we'll update the wiki to show how to setup for development and run the tests. JD -----Original Message----- From: "John Lam (IRONRUBY)" <[EMAIL PROTECTED]> To: "[email protected]" <[email protected]> Sent: 6/27/08 4:40 PM Subject: [Ironruby-core] r115 to SVN - foundational work for RubySpec integration is done These updates sync the SVN tree up to our internal repository as of today. My apologies for the delay in getting these new bits out to y'all – we've had challenges in integrating the new Ruby specs among other things. The external builds are now all delay signed using a test key – RubyTestKey.snk. This means that you *must* run the RunFirst.cmd file to enable skip verification of the public key that we used in the delay signing. Hopefully this resolves the various signing issues that folks outside have seen. The IronRuby.sln file and its related .csproj files have also been updated to not create random phantom directories (there's one left bin/FxCop gets generated, but I haven't been able to track down the culprit). But this should fix the problem that DeVaris ran into earlier. The Rakefile has been extensively updated as well – the foundations are in place to run the official RubySpec specs from their GIT repo. You'll need to get GIT installed and a few other things, but it should work. More on how to do this next week when that integration is done. Thanks, -John
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
