On 29 Mar 2011, at 11:31, Riccardo Mottola wrote:
Hi,
I run the tests on windows and they don't look so bright. I think we should try
to care about them! I run windows without ICU.
5461 Passed tests
58 Failed tests
11 Dashed hopes
9 Skipped sets
1 Failed file
Today I get 5642 passed, 17 failed, 16 dashed, 1 skipped.
$ grep Failed tests.log
Failed test: test00.m:88 ... +dateWithString:calendarFormat:locale: objects
to long timezone
Me too.
Failed test: general.m:44 ... newly created file is owned by current user
No, this passes for me.
Failed test: general.m:353 ... @encode(const char*) makes 'r*' type encoding
Me too ... it's a fairly trivial compiler bug on old compilers (like the one we
use on mingw).
Failed test: ../NSString/NSString_tests.h:309 ... character set
encoding/decoding works
Failed test: test00.m:102 ... NSDecimalNumber numberWithInt: works
Failed test: test00.m:107 ... NSDecimalNumber doubleValue works
Failed test: test00.m:111 ... NSDecimalNumber charValue works
Failed test: test00.m:113 ... NSDecimalNumber intValue works
Failed test: test00.m:115 ... NSDecimalNumber integerValue works
Failed test: test00.m:117 ... NSDecimalNumber longValue works
Failed test: test00.m:119 ... NSDecimalNumber longLongValue works
Failed test: test00.m:121 ... NSDecimalNumber shortValue works
Failed test: test00.m:123 ... NSDecimalNumber unsignedCharValue works
Failed test: test00.m:125 ... NSDecimalNumber unsignedIntValue works
Failed test: test00.m:127 ... NSDecimalNumber unsignedIntegerValue works
Failed test: test00.m:129 ... NSDecimalNumber unsignedLongValue works
Failed test: test00.m:133 ... NSDecimalNumber unsignedShortValue works
Failed file: test00.m aborted without running all tests!
Failed test: test01.m:229 ... Proxy GSFinePoint
The above all pass for me .. .and I've never seen them on a windows system.
Failed test: thread.m:182 ... A loop with an input source will block
This is a problem with reading from stdin :-(
Failed test: socket_cs.m:324 ... Local tcp (blocking open)
Failed test: socket_cs.m:354 ... Local socket
Failed test: socket_cs.m:385 ... Local socket (blocking open)
These three pass for me.
Failed test: NSString_tests.h:309 ... character set encoding/decoding works
Failed test: NSString_tests.h:309 ... character set encoding/decoding works
Failed test: order.m:23 ... UTF-16 BE OK
Failed test: order.m:35 ... UTF-16 LE OK
Failed test: order.m:48 ... UTF-32 BE OK
Failed test: order.m:61 ... UTF-32 LE OK
These are all fine for me.
Failed test: test02.m:251 ... /home/../nicola stringByStandardizingPath ==
/nicola
Failed test: test02.m:255 ... /here/and/there/../../nicola
stringByStandardizingPath == /here/nicola
Failed test: test02.m:259 ... /here/../../nicola stringByStandardizingPath
== /nicola
Failed test: test02.m:289 ... foo->bar absolute symlink expanded by
stringByResolvingSymlinksInPath
Failed test: test02.m:293 ... foo->bar relative symlink expanded by
stringByResolvingSymlinksInPath
Failed test: test02.m:302 ... /.. stringByStandardizingPath == /
Failed test: basic.m:78 ... Path of file URL /usr is /usr
Failed test: basic.m:80 ... File URL /usr is file://localhost/usr/
Failed test: basic.m:82 ... resourceSpecifier of /usr is //localhost/usr/
Failed test: basic.m:199 ... path quoting
Failed test: basic.m:206 ... complex -path
Failed test: basic.m:214 ... complex -absoluteString
Failed test: basic.m:215 ... complex -relativeString
Failed test: basic.m:216 ... complex -description
Failed test: basic.m:247 ... can load file URL with achor
These are all bugs in the testcases (now fixed) ... where the tests were
assuming unix filesystem layout which of course doesn't exist on windows.
Failed test: test00.m:121 ... respond with keepalive 0 (pause 0) OK
Failed test: test01.m:56 ... keep-alive test 0 OK
Failed test: test01.m:56 ... keep-alive test 1 OK
Failed test: test01.m:56 ... keep-alive test 2 OK
Failed test: test01.m:56 ... keep-alive test 3 OK
Failed test: test01.m:56 ... keep-alive test 4 OK
Failed test: test01.m:56 ... keep-alive test 5 OK
Failed test: test01.m:56 ... keep-alive test 6 OK
Failed test: test01.m:56 ... keep-alive test 7 OK
Failed test: test01.m:56 ... keep-alive test 8 OK
Failed test: test01.m:56 ... keep-alive test 9 OK
Failed test: test01.m:44 ... Got the correct data from a 200 - status load
Failed test: test01.m:46 ... 200 - status: Handle load succeeded
Failed test: test01.m:52 ... 401 - status: Handle load not loaded
(unanswered auth challenge)
Failed test: test01.m:58 ... 404 - status: Handle load not loaded (resource
not found)
These last URL loading ones fail for me too ... haven't had a chance to
investigate to find out why.