Your message dated Sat, 8 Jun 2024 16:46:46 +0200 with message-id <[email protected]> and subject line Re: Bug#1072642: curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest) has caused the Debian Bug report #1072642, regarding curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1072642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072642 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: curl Version: 8.8.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, I did a local rebuild on sid which failed: srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35 ~300 ~301 ~303 ~304 ~306 ~309 ~310 ~325 ~364 ~400 ~401 ~403 ~406 ~407 ~408 ~409 ~410 ~414 ~417 ~560 ~678 ~987 ~988 ~989 ~1112 ~1272 ~1470 ~1561 ~1562 ~1630 ~1631 ~1632 ~2034 ~2037 ~2041 ~3000 ~3001 ~3102 Using curl: ../src/curl [...] test 0241...[HTTP-IPv6 GET (using ip6-localhost)] 241: protocol FAILED! There was no content at all in the file log/5/server.input. Server glitch? Total curl failure? Returned: 7 == Contents of files in the log/5/ dir after test 241 === Start of file http_ipv6_server.log 16:19:15.385882 Running HTTP IPv6 version on port 36339 16:19:15.385966 Wrote pid 68256 to log/5/server/http_ipv6_server.pid 16:19:15.385990 Wrote port 36339 to log/5/server/http_ipv6_server.port 16:19:16.348256 ====> Client connect 16:19:16.348285 accept_connection 3 returned 4 16:19:16.348310 accept_connection 3 returned 0 16:19:16.348377 Read 88 bytes 16:19:16.348397 Process 88 bytes request 16:19:16.348427 Got request: GET /verifiedserver HTTP/1.1 16:19:16.348443 Are-we-friendly question received 16:19:16.348471 Wrote request (88 bytes) input to log/5/server.input 16:19:16.348499 Identifying ourselves as friends 16:19:16.348570 Response sent (56 bytes) and written to log/5/server.response 16:19:16.348589 special request received, no persistency 16:19:16.348604 ====> Client disconnect 0 === End of file http_ipv6_server.log === Start of file http_ipv6_verify.log * Trying [::1]:36339... * Connected to ::1 (::1) port 36339 > GET /verifiedserver HTTP/1.1 > Host: [::1]:36339 > User-Agent: curl/8.8.0 > Accept: */* > * Request completely sent off < HTTP/1.1 200 OK < Content-Length: 17 < { [17 bytes data] * Connection #0 to host ::1 left intact === End of file http_ipv6_verify.log === Start of file http_ipv6_verify.out WE ROOLZ: 68256 === End of file http_ipv6_verify.out === Start of file server.cmd Testnum 241 === End of file server.cmd === Start of file server.response HTTP/1.1 200 OK Content-Length: 17 WE ROOLZ: 68256 === End of file server.response === Start of file stderr241 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (7) Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't connect to server === End of file stderr241 === Start of file trace241 16:19:16.524170 == Info: Host ip6-localhost:36339 was resolved. 16:19:16.524215 == Info: IPv6: (none) 16:19:16.524217 == Info: IPv4: 31.15.64.248 16:19:16.524231 == Info: Trying 31.15.64.248:36339... 16:19:16.567508 == Info: connect to 31.15.64.248 port 36339 from 192.168.178.20 port 40168 failed: Connection refused 16:19:16.567523 == Info: Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't connect to server 16:19:16.567663 == Info: Closing connection === End of file trace241 [...] test 0507...[multi interface get with non-existing host name] lib507 returned 0, when expecting 6 507: exit FAILED == Contents of files in the log/31/ dir after test 507 === Start of file server.cmd Testnum 507 === End of file server.cmd === Start of file stderr507 URL: http://non-existing-host.haxx.se/ Test ended with result 0 === End of file stderr507 === Start of file stdout507 HTTP/1.1 200 OK Date: Wed, 05 Jun 2024 16:19:18 GMT Server: Apache/2.4.59 (Debian) Last-Modified: Sun, 14 Feb 2016 17:00:04 GMT ETag: "0-52bbdd4e2cd00" Accept-Ranges: bytes Content-Length: 0 Content-Type: text/html === End of file stdout507 [...] 2) TESTDONE: 1700 tests were considered during 522 seconds. TESTINFO: 195 tests were skipped due to these restraints: TESTINFO: "curl lacks debug support" 99 times (159, 356, 358, 359, 363, 412, 413, 437, 438 and 90 more) TESTINFO: "curl lacks unittest support" 49 times (1300, 1302, 1303, 1304, 1305, 1306, 1308, 1309, 1323 and 40 more) TESTINFO: "configured as DISABLED" 16 times (323, 594, 836, 882, 938, 1182, 1184, 1209, 1211 and 7 more) TESTINFO: "failed starting HTTP/2 server" 7 times (1700, 1701, 1702, 2402, 2403, 2404, 2405) TESTINFO: "curl lacks Schannel support" 6 times (2033, 2070, 2079, 2087, 3023, 3024) TESTINFO: "no gnutls-serv (with SRP support)" 4 times (320, 321, 322, 324) TESTINFO: "curl lacks http/3 support" 3 times (2500, 2502, 2503) TESTINFO: "curl has idn support" 3 times (959, 960, 961) TESTINFO: "curl lacks TrackMemory support" 2 times (96, 558) TESTINFO: "curl has ipv6 support" 1 time (1454) TESTINFO: "curl has threaded-resolver support" 1 time (506) TESTINFO: "curl has proxy support" 1 time (375) TESTINFO: "openssl engine not supported" 1 time (307) TESTINFO: "curl lacks NTLM_WB support" 1 time (1310) TESTINFO: "curl lacks Unicode support" 1 time (1703) IGNORED: failed tests: 587 TESTDONE: 1502 tests out of 1505 reported OK: 99% TESTFAIL: These test cases failed: 241 507 cu Andreas
--- End Message ---
--- Begin Message ---On 2024-06-07 Carlos Henrique Lima Melara <[email protected]> wrote: > On Wed, 5 Jun 2024 18:39:40 +0200 Andreas Metzler <[email protected]> wrote: [...] >> TESTFAIL: These test cases failed: 241 507 > Were you able to consistently get those exact failures? We are getting [...] > If you were able to consistently reproduce this, please let us know more > about your build environment. [...] Hello, I retried and got the same errors. However there was a local misconfiguration in the chroot. It a) lacked an entry for ip6-localhost in /etc/hosts but had b) a "domain" setting in the /etc/resolv.conf and c) ip6-localhost.this.domain actually resolved because of a wildcard entry. Adding ip6-localhost fixed 241, dropping the "domain" setting in the /etc/resolv.conf fixed 507. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
--- End Message ---
