Hello Guys, Thanks to Eric and his perseverance, we hunted down and killed almost all the pending errors and failures that stop RubyGems on Windows.
As for now, these are the results (Revision 1652): ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] 585 tests, 1734 assertions, 2 failures, 0 errors ruby 1.8.6 (2008-03-24 patchlevel 5000) [i386-mingw32] 585 tests, 1740 assertions, 2 failures, 0 errors Both are failing with the following: 1) Failure: test_install_no_wrappers(TestGemDependencyInstaller) [./test/test_gem_dependency_installer.rb:403]: </This file was generated by RubyGems./> expected to not match <"#!C:/Ruby/bin/ruby.exe\n#\n# This file was generated by RubyGems.\n#\n# The application 'a' is installed as part of a gem, and\n# this file is here to facilitate running it.\n#\n\nrequire 'rubygems'\n\nversion = \">= 0\"\n\nif ARGV.first =~ /^_(.*)_$/ and Gem::Version.correct? $1 then\n version = $1\n ARGV.shift\nend\n\ngem 'a', version\nload 'a_bin'\n">. 2) Failure: test_expand_and_validate_gem_dir(TestGemInstaller) [./test/test_gem_installer.rb:118]: <"c:/nonexistent"> expected but was <"d:/nonexistent">. == Based on the assertion count, it seems mingw build is doing some test mswin32 isn't.... anyway, I'll take another stab to these things tomorrow at lunch time :-) FYI: the first is the one related to binaries being changed when they shouldn't, the second one is just a problem with the location of code, since I'm not using C:/ drive to hold the code, I'm using D:/ Regards and good night everybody, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
