From: Jeff King <peff@peff.net>
To: Ivan Ivanov <qmastery16@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: Test "t0300-credentials" is failing on Arch/Artix: asks to enter the Username/Password in an infinite loop
Date: Fri, 6 Mar 2026 11:01:31 -0500 [thread overview]
Message-ID: <20260306160131.GA3577004@coredump.intra.peff.net> (raw)
In-Reply-To: <CAAaskFD7wmtqppatb5T5GMTviieR0Ttk9y4+c3khuF3bZBfE=g@mail.gmail.com>
On Fri, Mar 06, 2026 at 05:14:45PM +0300, Ivan Ivanov wrote:
> Friends, thank you so much for your kind help! Indeed: it turned out
> that if /dev/shm is mounted with noexec then "--root=/dev/shm" is
> failing. If you would like to ensure that the git tests are succeeding
> regardless of what are the mount flags on some system or what some
> distro's packagers are doing (more portability), maybe it is possible
> to modify the git test system - to make it so that "askpass" always
> gets launched from a native original directory, instead of being
> copied to some "root" place where it could fail?
it would be possible to do that, but introduce a lot of complexity.
Right now test scripts are given a single temporary scratch directory
with a repo to do whatever they want with. If we gave each one _two_
directories, one for putting executable things and one for repo
operations, then the latter could be on a noexec filesystem.
But why do we want to support pointing --root to a noexec filesystem in
the first place? I think this falls into "if it hurts, don't do it".
-Peff
next prev parent reply other threads:[~2026-03-06 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 0:42 Test "t0300-credentials" is failing on Arch/Artix: asks to enter the Username/Password in an infinite loop Ivan Ivanov
2026-03-06 1:05 ` Ivan Ivanov
2026-03-06 1:23 ` brian m. carlson
2026-03-06 1:44 ` Ivan Ivanov
2026-03-06 1:59 ` brian m. carlson
2026-03-06 2:14 ` Ivan Ivanov
2026-03-06 2:19 ` Ivan Ivanov
2026-03-06 4:38 ` Jeff King
2026-03-06 14:14 ` Ivan Ivanov
2026-03-06 16:01 ` Jeff King [this message]
2026-03-06 17:36 ` Ivan Ivanov
2026-03-06 21:17 ` brian m. carlson
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=20260306160131.GA3577004@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=qmastery16@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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