On 1/16/07, Berger, Daniel <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Cerberus > Sent: Tuesday, January 16, 2007 12:41 PM > To: rubygems-developers@rubyforge.org > Subject: [Rubygems-developers] [rubygems] Build broken by > drbrain (#1201) <snip> > 1) Failure: > test_class_build(TestGemExtRakeBuilder) > [./test/test_gem_ext_rake_builder.rb:35]: > <["rake > RUBYARCHDIR=C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_275 > 6/prefix > RUBYLIBDIR=C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756 > /prefix extension", "(in > C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756/ext)\n"]> > expected but was <["rake > RUBYARCHDIR=C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_275 > 6/prefix > RUBYLIBDIR=C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756 > /prefix extension", "(in > C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756/ext)\nrequ > ire_gem is obsolete. Use gem instead.\n"]>. Looks like the test suite needs an update here. > 2) Failure: > test_class_build_fail(TestGemExtRakeBuilder) > [./test/test_gem_ext_rake_builder.rb:45]: > <Gem::InstallError> exception expected but none was thrown. Not sure about this one.
It happens because of rake.bat (that came from OneClickInstaller) always returns 0 even in case of test failure. RubyGems tests expect that exception would be thrown (because of rake process return 1 "error" code) but it is not. This problem with rake.bat has been fixed in OneClickInstaller HEAD and I'll copy from it from repo to my distribution. It should fix test but take into account that other people that use released version of OneClickInst would have this issue.
3) Error: > test_install_bad_gem(TestInstaller): > Errno::EACCES: Permission denied - > C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756/gemhome/ca > che/broken-1.0.0.gem > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1281:in `unlink' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1281:in `remove_file' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1289:in > `platform_support' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1280:in `remove_file' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1269:in `remove' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:748:in `remove_entry' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1319:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1323:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:746:in `remove_entry' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:604:in `rm_r' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:600:in `rm_r' > ./test/gemutilities.rb:78:in `teardown' It looks like the test suite is trying to delete a file that's still in use, e.g. an open file handle. Windows doesn't allow this. > 4) Error: > test_install_with_message(TestInstaller): > Errno::EACCES: Permission denied - > C:/DOCUME~1/anatol/LOCALS~1/Temp/test_rubygems_2756/gemhome/ca > che/broken-1.0.0.gem > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1281:in `unlink' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1281:in `remove_file' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1289:in > `platform_support' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1280:in `remove_file' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1269:in `remove' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:748:in `remove_entry' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1319:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1323:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1318:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:1317:in > `postorder_traverse' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:746:in `remove_entry' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:604:in `rm_r' > c:/PROGRA~1/ruby/lib/ruby/1.8/fileutils.rb:600:in `rm_r' > ./test/gemutilities.rb:78:in `teardown' Same as above. None of these look like problems with gems so much as problems with the test suite.
Proposal to rubygems developers. Does it make sense to create separate maillist for Cerberus build result? Sometime I feel my guilt because of flooding rubygems developers maillist. -- anatol (http://feeds.feedburner.com/apomozov-eng)
_______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
