curl / Mailing Lists / curl-library / Single Mail
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.

Re: Test 1452 failing on ElectroBSD when executed with valgrind

From: Fabian Keil via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 29 Sep 2022 09:35:28 +0200

Timothe Litt via curl-library <curl-library_at_lists.haxx.se> wrote on 2022-09-25 at 10:29:51:

> Looks like to get anything useful from the telnet server log, you need
> to specify --verbose there.
>
> See curl/tests/negtelnetserver.py

As it turns out this can be enabled with runtest.pl's "-d" flag.

With it I get:

fk_at_t520 ~/git/curl/tests $./runtests.pl -v -d 1452
CMD (256): valgrind >/dev/null 2>&1
CMD (0): valgrind --help 2>&1 | grep -- --tool > /dev/null 2>&1
CMD (0): ../src/curl --version 1>log/curlverout.log 2>log/curlvererr.log
********* System characteristics ********
* curl 7.86.0-DEV (amd64-unknown-freebsd13.1)
* libcurl/7.86.0-DEV OpenSSL/1.1.1q zlib/1.2.12 libidn2/2.3.2 libpsl/0.21.1 (+libidn2/2.3.2) nghttp2/1.48.0
* Features: alt-svc AsynchDNS Debug HSTS HTTP2 HTTPS-proxy IDN IPv6 Largefile libz NTLM NTLM_WB PSL SSL threadsafe TLS-SRP TrackMemory UnixSockets
* Disabled:
* Host: t520.local
* System: ElectroBSD t520.local 13.1-STABLE ElectroBSD 13.1-STABLE #28 electrobsd-n252821-8ff5d83a0f97: Sat Sep 24 14:45:58 UTC 2022 fk_at_t520.local:/usr/obj/usr/src/amd64.amd64/sys/ELECTRO_BEER amd64
* OS: freebsd
*
*** DISABLES memory tracking when using threaded resolver
*
* Servers: SSL HTTP-IPv6 HTTP-unix FTP-IPv6
* Env: Valgrind
* Seed: 257280
* Unix socket paths:
* HTTP-Unix:http52019.sock
* Socks-Unix:/home/fk/git/curl/tests/socks52019.sock
*****************************************
DISABLED: test 323
DISABLED: test 594
DISABLED: test 836
DISABLED: test 882
DISABLED: test 938
DISABLED: test 1182
DISABLED: test 1184
DISABLED: test 1209
DISABLED: test 1211
DISABLED: test 1307
DISABLED: test 1316
DISABLED: test 1510
DISABLED: test 1512
DISABLED: test 1801
DISABLED: test 2086
DISABLED: test 2043
startnew: ./negtelnetserver.py --port 32151 --verbose 1 --pidfile ".telnet_server.pid" --logfile "log/telnet_server.log" --srcdir "."
2022-09-29 09:33:14,320 INFO [NTEL] Listening on ('localhost', 32151)
RUN: TELNET server PID 19262 port 32151
* pid neg TELNET => 19262 19262
test 1452...[Basic TELNET negotiation]
/usr/local/bin/valgrind --tool=memcheck --verbose --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind1452 ../src/curl --include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452 >log/stdout1452 2>log/stderr1452
2022-09-29 09:33:16,590 DEBUG [NTEL] Sending DO NEW_ENVIRON
2022-09-29 09:33:16,590 DEBUG [NTEL] Sending WILL NEW_ENVIRON
2022-09-29 09:33:16,591 DEBUG [NTEL] Sending DONT NAWS
2022-09-29 09:33:16,591 DEBUG [NTEL] Sending WONT NAWS
2022-09-29 09:33:16,628 DEBUG [NTEL] Starting negotiation (IAC)
2022-09-29 09:33:16,629 DEBUG [NTEL] In negotiation (WONT)
2022-09-29 09:33:16,629 DEBUG [NTEL] Client is unwilling
2022-09-29 09:33:16,629 DEBUG [NTEL] Option: NEW_ENVIRON
2022-09-29 09:33:16,632 DEBUG [NTEL] Starting negotiation (IAC)
2022-09-29 09:33:16,632 DEBUG [NTEL] In negotiation (WILL)
2022-09-29 09:33:16,632 DEBUG [NTEL] Client is willing
2022-09-29 09:33:16,632 DEBUG [NTEL] Option: BINARY
2022-09-29 09:33:16,633 DEBUG [NTEL] Starting negotiation (IAC)
2022-09-29 09:33:16,633 DEBUG [NTEL] In negotiation (DO)
2022-09-29 09:33:16,633 DEBUG [NTEL] Client can do
2022-09-29 09:33:16,634 DEBUG [NTEL] Option: BINARY
2022-09-29 09:33:16,634 DEBUG [NTEL] Starting negotiation (IAC)
2022-09-29 09:33:16,634 DEBUG [NTEL] In negotiation (WILL)
2022-09-29 09:33:16,634 DEBUG [NTEL] Client is willing
2022-09-29 09:33:16,634 DEBUG [NTEL] Option: SUPPRESS_GO_AHEAD
2022-09-29 09:33:16,635 DEBUG [NTEL] Starting negotiation (IAC)
2022-09-29 09:33:16,635 DEBUG [NTEL] In negotiation (DO)
2022-09-29 09:33:16,635 DEBUG [NTEL] Client can do
2022-09-29 09:33:16,635 DEBUG [NTEL] Option: SUPPRESS_GO_AHEAD
2022-09-29 09:33:16,638 DEBUG [NTEL] Incoming data: bytearray(b'test1452\n')
2022-09-29 09:33:16,638 DEBUG [NTEL] Received normal request - echoing back
2022-09-29 09:33:16,639 DEBUG [NTEL] Sending b'test1452'
CMD (14336): /usr/local/bin/valgrind --tool=memcheck --verbose --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind1452 ../src/curl --include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452 >log/stdout1452 2>log/stderr1452

curl returned 56, when expecting 0
 exit FAILED

 - abort tests
* kill pid for telnet => 19262
RUN: Process with pid 19262 signalled to die
RUN: Process with pid 19262 forced to die with SIGKILL
TESTDONE: 1 tests were considered during 3 seconds.
TESTDONE: 0 tests out of 1 reported OK: 0%

TESTFAIL: These test cases failed: 1452

So it seems to me that the telnet server isn't at fault here.

> Beyond that, I'll let someone closer to the tests take over.

Thanks for your replies.

Fabian


-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
Received on 2022-09-29