Hello,

I've run into a suspicious failure of test513 while trying to build
packages for s390:

https://brewweb.devel.redhat.com/getfile?taskID=2123396&name=build.log

I am trying to investigate what happens for several hours, no idea so far.
The failure appears only on s390 and only in test513. It's *almost* 100%
reproducible. I am completely puzzled and can't figure out how the test513
differs from other tests, which work just fine on the same system.

I compared the test logs of test513 on a working machine and s390. The only
difference is this:

--- log/check-expected 2009-12-03 13:20:44.000000000 -0500
+++ log/check-generated 2009-12-03 13:20:44.000000000 -0500
@@ -1,6 +0,0 @@
-POST /513 HTTP/1.1
-Host: 127.0.0.1:8990
-Accept: */*
-Content-Length: 1
-Content-Type: application/x-www-form-urlencoded
-
== Contents of files in the log/ dir after test 513
=== Start of file check-expected
 POST /513 HTTP/1.1
 Host: 127.0.0.1:8990
 Accept: */*
 Content-Length: 1
 Content-Type: application/x-www-form-urlencoded
=== End of file check-expected

curl.log, server.input, stderr513 are the some in both cases.

How is the file "log/check-generated" actually generated?

If the file is generated from stderr513, then it looks like a perl bug to me.
But I still can't image how such a bug could be specific to test513.

Thanks in advance for any hints!

Kamil
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2009-12-03