Re: 8.3.0: test1474 fails every time
On Sun, Sep 17, 2023 at 10:43:17PM +0200, Christian Weisgerber via curl-library wrote: > The comment for test1474 says "This test is quite timing dependent and > tricky to set up." On OpenBSD, it fails every time for me. And this > is not an overloaded machine. I've noticed failures on the NetBSD autobuilds as well, but I've been unable to successfully install NetBSD in a VM to test it. Maybe I'll have more luck with OpenBSD. What I noticed in the NetBSD logs is that rather than receiving an initial 64 KiB block of data, it looks like on NetBSD it's only receiving closer to 48 KiB. I wanted to try this patch on NetBSD to see if it's related to Nagle's algorithm, but couldn't get to the point where I could try it: diff --git a/tests/data/test1474 b/tests/data/test1474 index 848f15211..24b349b19 100644 --- a/tests/data/test1474 +++ b/tests/data/test1474 @@ -82,7 +82,7 @@ http HTTP PUT with Expect: 100-continue and 417 response during upload -http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -T %LOGDIR/test%TESTNUMBER.txt --limit-rate 64K --expect100-timeout 0.001 +http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -T %LOGDIR/test%TESTNUMBER.txt --limit-rate 64K --expect100-timeout 0.001 --tcp-nodelay # Must be large enough to trigger curl's automatic 100-continue behaviour It's a finicky test (which is why it's marked flaky) but it should work fine on an unloaded system. Dan -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
8.3.0: test1474 fails every time
The comment for test1474 says "This test is quite timing dependent and tricky to set up." On OpenBSD, it fails every time for me. And this is not an overloaded machine. The initial part of the trace suggests that none of the timing happens as intended: 15:38:42.282589 == Info: Trying 127.0.0.1:18792... 15:38:42.283011 == Info: Connected to 127.0.0.1 (127.0.0.1) port 18792 15:38:42.283055 => Send header, 137 bytes (0x89) : PUT /we/want/1474 HTTP/1.1 001c: Host: 127.0.0.1:18792 0033: User-Agent: curl/8.3.0 004b: Accept: */* 0058: Content-Length: 1053701 0071: Expect: 100-continue 0087: 15:38:42.288525 <= Recv header, 27 bytes (0x1b) : HTTP/1.1 417 BAD swsbounce. 15:38:42.288733 <= Recv header, 36 bytes (0x24) : Date: Tue, 09 Nov 2010 14:49:00 GMT. 15:38:42.288758 <= Recv header, 25 bytes (0x19) : Server: test-server/fake. 15:38:42.288764 <= Recv header, 18 bytes (0x12) : Content-Length: 0. 15:38:42.288770 == Info: Got HTTP failure 417 while waiting for a 100 15:38:42.288773 <= Recv header, 1 bytes (0x1) : . 15:38:42.20 == Info: Connection #0 to host 127.0.0.1 left intact I don't know if this points to a problem in curl or--more likely, I suspect--in the test. I'm attaching an archive of the log directory. -- Christian "naddy" Weisgerber na...@mips.inka.de log.tgz Description: application/gtar-compressed -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
