From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Amogh Dambal <amoghdambal1@gmail•com>
Cc: 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 22:18:19 +0000 [thread overview]
Message-ID: <ahTKq_zCmEDJpoN5@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <23221493-ea81-47c3-9647-6c6ac8d03360@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
On 2026-05-25 at 22:01:23, Amogh Dambal wrote:
> `GIT_TEST_OPTS=--verbose` was very illuminating. I captured STDOUT/STDERR:
> `make test GIT_TEST_OPTS=--verbose &> git-test-verbose-fail.tmp`, which
> shows that almost every test fails `check_config` because a `git init` is
> creating a `.git/config` file whose executable bit is set:
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.
> --
> Initialized empty Git repository in /root/git/t/trash
> directory.t0001-init/plain/.git/
> plain/.git/config is executable?
> not ok 1 - plain
>
> [...]
>
>
> However, I'm not able to reproduce this, e.g. directly using the local built
> binary seems to work fine:
>
> mkdir -p /tmp/debug && cd /tmp/debug
> /root/git/git init plain
> ls -alhrt /tmp/debug/plain/.git
> root@ec94ab1b260e:/tmp/debug# ls -alhrt /tmp/debug/plain/.git
> total 24K
> -rw-r--r-- 1 root root 92 May 25 21:26 config
> drwxr-xr-x 3 root root 4.0K May 25 21:26 ..
> drwxr-xr-x 4 root root 4.0K May 25 21:26 refs
> drwxr-xr-x 4 root root 4.0K May 25 21:26 objects
> -rw-r--r-- 1 root root 23 May 25 21:26 HEAD
> drwxr-xr-x 4 root root 4.0K May 25 21:26 .
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.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]
next prev parent reply other threads:[~2026-05-25 22:18 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 [this message]
2026-05-25 22:25 ` Amogh Dambal
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=ahTKq_zCmEDJpoN5@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=amoghdambal1@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mmontalbo@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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