Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
8.3.0: test1474 fails every time
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Christian Weisgerber via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 17 Sep 2023 22:43:17 +0200
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)
0000: 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)
0000: HTTP/1.1 417 BAD swsbounce.
15:38:42.288733 <= Recv header, 36 bytes (0x24)
0000: Date: Tue, 09 Nov 2010 14:49:00 GMT.
15:38:42.288758 <= Recv header, 25 bytes (0x19)
0000: Server: test-server/fake.
15:38:42.288764 <= Recv header, 18 bytes (0x12)
0000: 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)
0000: .
15:38:42.288880 == 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.
Received on 2023-09-17
Date: Sun, 17 Sep 2023 22:43:17 +0200
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)
0000: 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)
0000: HTTP/1.1 417 BAD swsbounce.
15:38:42.288733 <= Recv header, 36 bytes (0x24)
0000: Date: Tue, 09 Nov 2010 14:49:00 GMT.
15:38:42.288758 <= Recv header, 25 bytes (0x19)
0000: Server: test-server/fake.
15:38:42.288764 <= Recv header, 18 bytes (0x12)
0000: 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)
0000: .
15:38:42.288880 == 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 naddy_at_mips.inka.de
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- application/x-gtar-compressed attachment: log.tgz