Re: test suite base

[Richard Frith-Macdonald]

On 5 Mar 2009, at 20:53, David Wetzel wrote:

> Hi folks,
>
> I tried the test suite on a NetBSD amd64 VM:
>
> runtests.sh base
> --- Running tests in base ---
>
> base/NSBundle/general.m:
> FAIL: -classNamed returns the correct class
> FAIL: -executablePath returns an executable path (gnustep bundle)

These two should not happen ... probably a bug you need to track down  
in the bundle code for determining the path to the executable.
This may well be OS and possibly architecture dependent.

> base/NSConnection/connection.m:
> FAIL: NSConnection can do a simple connection

This should not happen, but is most likely an ffcall/libffi issue

> base/NSPointerArray/basic.m:
> EXCEPTION: NSGenericException method encodeWithCoder: not  
> implemented in NSConcretePointerArray(instance) (null)
> UNRESOLVED: test_NSCoding object 0
> FAIL: Object 0 of class 'NSPointerArray' is retained by copy with  
> same zone

This is expected ... NSPointerArray is a new class and I've not  
figured out how to do coding for it.  The Apple documentation says it  
implementes the NSCoding protocol, but the Apple implementation  
doesn't work either.

> base/NSProxy/test01.m:
> FAIL: base/NSProxy/test01.m

This is probably a the ffcall/libfii problem, and is most likely an  
easier place to look to start fixing it than  the NSConnection code.

> base/NSStream/socket.m:
> FAIL: base/NSStream/socket.m

I don't think this should be failing, but I have no idea what the  
cause might be.