Skip to content

curl 8.1.0: tests 1467 1468 failing with 'socket path too long' #11152

Closed

Description

@citrus-it

When running the testsuite after updating from curl 8.0.1 to 8.1.0, tests 1467 and 1468 are failing, with this message on stderr:

curl: (6) Unix socket path too long: '/data/omnios-build/omniosorg/bloody/_build/curl-8.1.0/curl-8.1.0-build/build.i386/tests/log/server/socks.sock'

On my build system, that path is indeed > 107 characters (the size of sockaddr_un.sun_path being 108).

This seems to be a result of 89ede39

CMD (0): ../src/curl --version 1>log/curlverout.log 2>log/curlvererr.log
********* System characteristics ********
* curl 8.1.0 (x86_64-pc-solaris2.11)
* libcurl/8.1.0 OpenSSL/3.0.8 zlib/1.2.13 brotli/1.0.9 zstd/1.5.5 nghttp2/1.52.0
* Features: alt-svc AsynchDNS brotli HSTS HTTP2 HTTPS-proxy IPv6 Largefile libz NTLM NTLM_WB SSL threadsafe TLS-SRP UnixSockets zstd
* Disabled: xattr
* Host: bloody
* System: SunOS bloody 5.11 omnios-master-42fe848aa52 i86pc i386 i86pc
* OS: solaris
* Env:
* Seed: 214771
* Servers: HTTP-IPv6 HTTP-unix FTP-IPv6
*****************************************
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: perl -I../../../src/tests ../../../src/tests/http-server.pl --keepalive 30 --pidfile "log/server/http_server.pid" --logfile "log/http_server.log" --logdir "log" --portfile log/server/http_server.port --config log/ftpserver.cmd --ipv4 --port 0 --srcdir "../../../src/tests"
RUN: ../src/curl --max-time 13 --output log/http_verify.out --silent --verbose --globoff "http://127.0.0.1:38366/verifiedserver" 2>log/http_verify.log
CMD (0): ../src/curl --max-time 13 --output log/http_verify.out --silent --verbose --globoff "http://127.0.0.1:38366/verifiedserver" 2>log/http_verify.log
RUN: HTTP server is on PID 149 port 38366
* pid http => 149 149
startnew: server/socksd --pidfile log/server/socks2_server.pid --reqfile log/socksd-request.log --logfile log/socks2_server.log --unix-socket log/server/socks.sock --backend 127.0.0.1 --config log/ftpserver.cmd
RUN: SOCKS2 server is now running PID 158
* pid socks5unix => 158 158
test 1467...[HTTP GET via SOCKS5 proxy via unix sockets]
../src/curl --output log/curl1467.out  --include --trace-ascii log/trace1467 --trace-time --socks5 localhostlog/server/socks.sock http://127.0.0.1:38366/1467 > log/stdout1467 2> log/stderr1467
CMD (1536): ../src/curl --output log/curl1467.out  --include --trace-ascii log/trace1467 --trace-time --socks5 localhostlog/server/socks.sock http://127.0.0.1:38366/1467 > log/stdout1467 2> log/stderr1467

 1467: protocol FAILED!
 There was no content at all in the file log/server.input.
 Server glitch? Total curl failure? Returned: 6

 - abort tests
* kill pid for socks5unix => 158
* kill pid for http => 149
RUN: Process with pid 149 signalled to die
RUN: Process with pid 158 signalled to die

RUN: Process with pid 149 forced to die with SIGKILL
RUN: Process with pid 158 forced to die with SIGKILL
TESTDONE: 1 tests were considered during 2 seconds.
TESTDONE: 0 tests out of 1 reported OK: 0%

TESTFAIL: These test cases failed: 1467
bloody:omnios:% uname -a
SunOS bloody 5.11 omnios-master-42fe848aa52 i86pc i386 i86pc

bloody:omnios:% rg -A3 sockaddr_un /usr/include/sys/un.h
53:struct     sockaddr_un {
54-   sa_family_t     sun_family;             /* AF_UNIX */
55-   char            sun_path[108];          /* path name (gag) */
56-};

Activity

  1. added 2 commits that reference this issue on May 20, 2023
    32883b9
    05b86f7
  2. self-assigned this
    on May 22, 2023
  3. added a commit that references this issue on Jul 19, 2023
    d1a63f8
  4. added a commit that references this issue on Sep 25, 2023
    4583d96
  5. added a commit that references this issue on Mar 27, 2024
    8cf4189
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions