From: "Berger, Daniel" Date: 2007-03-06T09:18:41+09:00 Subject: Re: Ruby 1.8.6 preview3 has been released > -----Original Message----- > From: Joel VanderWerf [mailto:vjoel@path.berkeley.edu] > Sent: Sunday, March 04, 2007 12:22 PM > To: ruby-core@ruby-lang.org > Subject: Re: Ruby 1.8.6 preview3 has been released > > > Akinori MUSHA wrote: > > Hi, > > > > I am pleased to announce that the third preview of Ruby > 1.8.6 has been > > released. This release is expected to be a candidate for the final > > release, and all of you are welcome and invited to the > final testing. > ... > > After five-odd full days of public preview and testing, the final > > release will take place. It will hopefully occur on next weekend. > > Those of us who build ruby regularly have been eagerly > downloading and > testing these releases, but I wonder about something... > > How widely tested on Windows are these releases? Are there enough > Windows developers who build from source (rather than use the OCI)? Here are the results of an 'nmake test-all' that I ran on a Windows XP SP 2 box, using VC++ 8.0: 1417 tests, 13318 assertions, 3 failures, 55 errors The good news is that all of the core tests pass, and all but one of the errors come from what appears bugs in the SOAP tests. It looks like the usual culprit - trying to delete files before closing the associated file handle. The other failure comes from Pathname: 1) Failure: test_del_trailing_separator_25(TestPathname) [./test/pathname/test_pathname.rb:27]: del_trailing_separator("\225\\\\"). <"\225\\"> expected but was <"\225">. That being said, I'm not really satisified with the Ruby test suite in general, especially not for MS Windows, so take the overall success of the test suite with a grain of salt. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.