You're right, it looks like it's not a serious failure.

I looked at the log directory and saw the following:

/home/tooldev/curl/curl-7.14.1/tests/log: vi check-expected
"check-expected" 10 lines, 169 characters
POST /that.site.com/56 HTTP/1.1^M
Host: 127.0.0.1:8990^M
Accept: */*^M
Transfer-Encoding: chunked^M
Content-Type: application/x-www-form-urlencoded^M
^M
c^M
we post this^M
0^M
^M

/home/tooldev/curl/curl-7.14.1/tests/log: vi check-generated
"check-generated" 9 lines, 167 characters
POST /that.site.com/56 HTTP/1.1^M
Host: 127.0.0.1:8990^M
Accept: */*^M
Transfer-Encoding: chunked^M
Content-Type: application/x-www-form-urlencoded^M
^M
c^M
we post this^M
0^M

It would seem that the generated output is missing the last empty line
that is present in the expected output.
How can this be fixed?
Our compile scripts won't pass a build of curl without all tests passing.
It looks like this is an error in the test suite.
But how to fix it?

--- Original message ---

First, I seriously doubt that this test failure actually is a serious and true
failure in the curl code. Most test case failures that happen like this are
due to flaws and shortcomings in the test servers or test scripts.

That said, tou can do this to investigate and debug:

cd into the 'tests' dir and run only test 56 like this:

$ ./runtests.pl 56

If it still fails, it leaves its output files in the log/ dir (and it it
doesn't fail you can force it to leave those files there by using runtests.ok
-k)

If this doesn't cover most of it, ask again!

        
                
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
Received on 2005-09-06