public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Ivan Ivanov <qmastery16@gmail.com>
Cc: Jeff King <peff@peff.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 21:17:25 +0000	[thread overview]
Message-ID: <aatEZfGPkZTVT4uJ@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <CAAaskFBNBEiPW4tLRtPQqkntHFpDTgjwrx8Lqg-qax1Cb_mEhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

On 2026-03-06 at 17:36:35, Ivan Ivanov wrote:
> Sounds reasonable, but - if there is only an issue with askpass and
> everything else is fine, couldn't we just execute askpass from its
> origin - instead of copying it to the destination ./git-test/
> directory?

We actually do generate and run quite a few scripts in the testsuite
(`git grep write_script`).  All of these will be generated in the trash
directory we create for each test and some of them contain dynamic
components that cannot be generated before the testsuite is run.

It may be, for whatever reason, that only those tests happen to
malfunction in this case, but we're not willing to do the testing and
maintenance required to guarantee that the testsuite works in a noexec
environment.  There are some cases where we accept patches to deal with
uncommon cases (for instance, I send in patches to fix the testsuite
with zsh in sh mode from time to time), but I think this is a case where
we fully expect things to be very broken (at least I do) and the amount
of effort required to fix it would be substantial.

I am sympathetic to the downsides of noexec temporary directories
because I've worked on systems where `/tmp` was noexec, but we assume
that most people on Unix systems have at least a home directory where
they can execute things (if for no other reason than the customary
`~/bin` directory).
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2026-03-06 21:17 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
2026-03-06 17:36                 ` Ivan Ivanov
2026-03-06 21:17                   ` brian m. carlson [this message]

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=aatEZfGPkZTVT4uJ@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=qmastery16@gmail.com \
    /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