From: Collin Funk <collin.funk1@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: git@vger.kernel.org
Subject: Re: t7528-signed-commit-ssh.sh fails due to ssh-agent fails to start with ENAMETOOLONG
Date: Thu, 16 Oct 2025 19:06:44 -0700 [thread overview]
Message-ID: <87o6q6nux7.fsf@gmail.com> (raw)
In-Reply-To: <4e2952e512afc780b621d2c153b3e6e4eb7ed89a.camel@xry111.site>
Hi Xi,
Xi Ruoyao <xry111@xry111.site> writes:
> When I test git-2.51.1 I hit a test failure in t7528-signed-commit-
> ssh.sh. Running it with -v reveals:
>
> unix_listener_tmp: path "/home/xry111/sources/12.5/git-2.51.1/t/trash directory.t7528-signed-commit-ssh/.ssh/agent/s.fTyCxA5V6V.agent.dX2yNWQUX5" too long for Unix domain socket
> main: Couldn't prepare agent socket
>
> So this seems an issue in the test harness. Is it possible to fix it?
Unix sockets have an unfortunate historical limit of ~100 characters on
most systems. All the derivatives of 4.4BSD have a limit of 104
characters. Linux has a limit of 108 characters [1]. AIX is nice and
supports 1024 characters, but I assume you are not using that.
I guess this test can check for that error. I'll have a look.
Collin
[1] https://github.com/torvalds/linux/blob/98ac9cc4b4452ed7e714eddc8c90ac4ae5da1a09/include/uapi/linux/un.h#L7
next prev parent reply other threads:[~2025-10-17 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 1:52 t7528-signed-commit-ssh.sh fails due to ssh-agent fails to start with ENAMETOOLONG Xi Ruoyao
2025-10-17 2:06 ` Collin Funk [this message]
2025-10-17 7:09 ` Jeff King
2025-10-17 9:52 ` Lauri Tirkkonen
2025-10-17 10:54 ` Jeff King
2025-10-17 19:31 ` brian m. carlson
2025-10-18 9:56 ` Jeff King
2025-10-17 17:42 ` Junio C Hamano
2025-10-18 9:51 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o6q6nux7.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=git@vger.kernel.org \
--cc=xry111@xry111.site \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).