I just ran "./configure --with-ssl --enable-debug --enable-ipv6" in the
current build directory, then built curl by hand. When I ran the tests
it passed everything up to here:

test 400...SKIPPED
* Test 400: server problems
test 401...SKIPPED
* Test 401: server problems
test 402...SKIPPED
* Test 402: server problems
test 403...SKIPPED
* Test 403: server problems
test 500...[simple libcurl HTTP GET tool]

 data FAILED:
--- .expected Tue Feb 24 01:56:08 2004
+++ .generated Tue Feb 24 01:56:08 2004
@@ -1,12 +0,0 @@
-HTTP/1.1 200 OK
-Date: Thu, 09 Nov 2010 14:49:00 GMT
-Server: test-server/fake
-Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
-ETag: "21025-dc7-39462498"
-Accept-Ranges: bytes
-Content-Length: 6
-Connection: close
-Content-Type: text/html
-Funny-head: yesyes
-
-<foo>

 - abort tests
TESTDONE: 157 tests out of 158 reported OK: 99%
TESTFAIL: These test cases failed: 500
TESTDONE: 162 tests were considered.
TESTINFO: 4 tests were skipped due to these restraints:
TESTINFO: "server problems" 4 times (400, 401, 402, 403)

Daniel Stenberg wrote:

>Hi friends
>
>As can be seen in a recent autobuild log provided by Ralph Mitchell...
>
> http://curl.haxx.se/auto/log.cgi?id=20040222214238-23448
>
>... several test cases fail when run on his NetBSD on sparc.
>
>Since most of these are old tests doing nothing new, I'm of course curious
>about the reasons for them. Is there possibly someone else with NetBSD that
>can either confirm that these have happened before on NetBSD, or that can say
>that NetBSD usually can run all tests fine?
>
>Ralph, can you run one or a few of the failing tests manually to see if you
>can figure out in more detail what happens? The logs produced in tests/log
>(available after a failure) might reveal further info.
>
>
>
Received on 2004-02-25