From: Amogh Dambal <amoghdambal1@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>, Michael Montalbo <mmontalbo@gmail.com>,
git@vger.kernel.org
Subject: Re: Expected test suite behavior
Date: Mon, 25 May 2026 15:25:11 -0700 [thread overview]
Message-ID: <4649049a-ded5-4cc6-bc2b-d5f543e6df99@gmail.com> (raw)
In-Reply-To: <ahTKq_zCmEDJpoN5@fruit.crustytoothpaste.net>
> What are the OS and file system on the host? We tend to see
> executable bits set when NTFS, FAT, or other Windows-adjacent file
> systems are used on Linux and you're mounting `$(PWD)` into the
> container as a volume.
Ah, this is a smoking gun. I'm not on a Windows-adjacent file system;
I'm running macOS Sequoia 15.5 on the host. Specifically:
$ uname -msprsv
Darwin 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:26 PDT
2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8112 arm64 arm
But I am mounting $(PWD) into the container as a volume.
> Git doesn't use `/tmp` for most files in the tests. Those are stored
> under `t/`, so you'd want to create your test directory there.
ACK, good to know, thanks! I am still seeing the same behavior with a
`debug` directory under `t/`:
root@ec94ab1b260e:~/git/t/debug# /root/git/git init plain
root@ec94ab1b260e:~/git/t/debug# ls -alhrt
/root/git/t/debug/plain/.git/config
-rw-r--r-- 1 root root 111 May 25 22:24 /root/git/t/debug/plain/.git/config
next prev parent reply other threads:[~2026-05-25 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 6:20 Expected test suite behavior Michael Montalbo
2026-05-25 7:27 ` Jeff King
2026-05-25 22:01 ` Amogh Dambal
2026-05-25 22:18 ` brian m. carlson
2026-05-25 22:25 ` Amogh Dambal [this message]
2026-05-26 0:41 ` brian m. carlson
2026-05-26 1:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 5:38 Amogh Dambal
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=4649049a-ded5-4cc6-bc2b-d5f543e6df99@gmail.com \
--to=amoghdambal1@gmail.com \
--cc=git@vger.kernel.org \
--cc=mmontalbo@gmail.com \
--cc=peff@peff.net \
--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