[MacRuby-devel] Interesting spec failures

Laurent Sansonetti lsansonetti at apple.com
Mon Oct 12 12:22:51 PDT 2009

Hi Gp,

Yes there are several environmental issues when running RubySpec. For  
example I noticed that it will fail if you have a /tmp/xxx directory  
or if your $HOME is actually a symlink.

On Claudio's server I noticed a few more problems (you can see the  
failures from the nightly build website, under Tests).

One of my biggest issues with RubySpec is that it executes everything  
within the same process, so one spec could potentially damage the  
environment (because of a bug) so that another one might not pass (but  
executing a spec separately would work).


On Oct 12, 2009, at 11:39 AM, Giampiero De Ciantis wrote:

> I have been trying to run the specs and have found some weird issues  
> with some of the behaviour
> spec/frozen/core/kernel/spawn_spec.rb - in the "Kernel uses the  
> current working directory as its working directory" it fails the  
> test, but if you change the command line to use MacRuby instead of  
> Ruby, it passes.
> spec/frozen/library/socket/ipsocket/getaddress_spec.rb - in the  
> "Socket::IPSocket#getaddress raises an error on unknown hostnames."  
> The spec fails, but if run the same test on macirb it raises the  
> appropriate socket error on an unknown host name.
> Anyone know of environmental issues that might be causing this? I do  
> 'rake clean' often and still get these errors.
> I am also getting an error "cat: stdin: Bad file descriptor" on the / 
> spec/frozen/core/io/close_read_spec.rb spec, but it still passes.
> Cheers,
> -Gp
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

More information about the MacRuby-devel mailing list