It was marked as critical before the spec update (I sent you an email), which means we did look into it when it first started failing. I did look into the failure (not knowing that it was previously tagged as critical) and know what is causing the problem, and it is a race. It will fail on your machine and in Snap given enough time.
We should not be untagging such non-deterministic critical and unstable failures. Otherwise we end up spending time investigating the failures everytime. Do you know if any other critical and unstable tags were removed? Would be good to send the list of such removed tags to the team after a RubySpec update so folks can keep an eye out for the failures. -----Original Message----- From: Jim Deville Sent: Tuesday, January 19, 2010 9:50 AM To: Shri Borde; IronRuby External Code Reviewers Cc: ironruby-core@rubyforge.org Subject: RE: Code Review: More ActionPack fixes Since the send_spec tag is working on my machine and snap, I'd like to try to figure out why it's failing for you instead of disabling it. JD -----Original Message----- From: Shri Borde Sent: Tuesday, January 19, 2010 12:44 AM To: IronRuby External Code Reviewers Cc: ironruby-core@rubyforge.org Subject: Code Review: More ActionPack fixes tfpt review "/shelveset:rails;REDMOND\sborde" Comment : defined? should clear $! of any exception that may have been thrown by const_missing Makes NativeMethods.SetEnvironmentVariable check if the call succeeded Adds a critical tag for library\socket\basicsocket\send_spec as it hung on my machine _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
