diff options
| author | Dan Fandrich <dan@coneharvesters.com> | 2015-03-21 23:57:32 +0100 |
|---|---|---|
| committer | Dan Fandrich <dan@coneharvesters.com> | 2015-03-22 00:03:44 +0100 |
| commit | 148207e2d76c75dec101479adc947f1734c78139 (patch) | |
| tree | f00e6be21ddb49d9584ee9cef447933b769405ad | |
| parent | 7f5a17044281bae546ff749543caa68c2a2443d6 (diff) | |
test1513: eliminated race condition in test run
It seems that some systems (e.g. fairly consistently in some recent
Solaris autobuilds) would manage to get to the connect phase before the
progress callback was called, resulting in a CURLE_COULDNT_CONNECT
error. Reworked the test to point at a test server that never returns a
full result so the progress callback always gets a chance to be called
before the transfer can complete in some other way.
| -rw-r--r-- | tests/data/test1513 | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/tests/data/test1513 b/tests/data/test1513 index 4a63f1806..8abb96fa6 100644 --- a/tests/data/test1513 +++ b/tests/data/test1513 @@ -7,16 +7,20 @@ PROGRESSFUNCTION # Server-side <reply> +<data nocheck="yes"> +HTTP/1.1 204 PARTIAL
+X-Comment: partial response to keep the client waiting
+</data> +<postcmd> +wait 10 +</postcmd> </reply> # Client-side <client> <server> -none -</server> -<features> http -</features> +</server> <tool> lib1513 </tool> @@ -26,7 +30,7 @@ return failure immediately from progress callback # this server/host won't be used for real <command> -http://localhost/1513 +http://%HOSTIP:%HTTPPORT/1513 </command> </client> |