From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] test-lib.sh: try to re-chmod & retry on failed trash removal
Date: Sun, 10 Oct 2021 15:14:02 -0700 [thread overview]
Message-ID: <xmqqee8seded.fsf@gitster.g> (raw)
In-Reply-To: <patch-1.1-d7e88a77fef-20211009T133043Z-avarab@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 9 Oct 2021 15:31:02 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> This can be demonstrated as e.g. (output snipped for less verbosity):
>
> $ ./t0004-unwritable.sh --run=3 --immediate
> ok 1 # skip setup (--run)
> ok 2 # skip write-tree should notice unwritable repository (--run)
> not ok 3 - commit should notice unwritable repository
> [...]
> $ ./t0004-unwritable.sh --run=3 --immediate
> rm: cannot remove '[...]/trash directory.t0004-unwritable/.git/objects/info': Permission denied
> FATAL: Cannot prepare test area
> [...]
>
> I.e. if any of its tests failed, and the tests were being run under
> "--debug"[2] or "--immediate"[3] (which was introduced after [1]) we
> wouldn't re-chmod the object directory. We'd then fail on the next run
> since the test setup couldn't remove the trash files.
OK, the first thing these scripts do is to create $TRASH_DIRECTORY
for their own use, and that is what fails (hence "Cannot prepare").
And making sure we try harder to prepare would be a good thing.
Given that understanding of the motivation...
> @@ -1210,10 +1210,10 @@ test_done () {
...it is puzzling why we are touching the code that happens _after_
a test is run. If our philosophy is to leave the mess after a test
fails so that the debugging person can take a look without
contaminating the forensics data, but blindly and forcibly clean up
before starting a new round, reusing the "do more than usual to
remove" logic meant to be used for the latter here feels counter
productive and also a bit counter intuitive.
> error "Tests passed but trash directory already removed before test cleanup; aborting"
>
> cd "$TRASH_DIRECTORY/.." &&
> - rm -fr "$TRASH_DIRECTORY" || {
> + remove_trash_directory "$TRASH_DIRECTORY" || {
> # try again in a bit
> sleep 5;
> - rm -fr "$TRASH_DIRECTORY"
> + remove_trash_directory "$TRASH_DIRECTORY"
> } ||
> error "Tests passed but test cleanup failed; aborting"
> fi
> +# Try really hard to clean up our mess
> +remove_trash_directory() {
> + dir="$1"
> + if ! rm -rf "$dir"
> + then
> + say_color info >&3 "Failed to remove trash directory, trying to re-chmod it first..."
> + chmod -R u+w "$dir" 2>/dev/null
If a test lost searchable bit from directories, "u+wx" may be
necessary to clean fully, no?
> + rm -rf "$dir"
> + fi
> + ! test -d "$dir"
> +}
> +
On the other hand...
> # Are we running this test at all?
> remove_trash=
> this_test=${0##*/}
> @@ -1388,7 +1400,7 @@ GNUPGHOME="$HOME/gnupg-home-not-used"
> export HOME GNUPGHOME USER_HOME
>
> # Test repository
> -rm -fr "$TRASH_DIRECTORY" || {
> +remove_trash_directory "$TRASH_DIRECTORY" || {
... this one does make sense and matches what the proposed log
message sold us the change as.
> GIT_EXIT_OK=t
> echo >&5 "FATAL: Cannot prepare test area"
> exit 1
Thanks.
next prev parent reply other threads:[~2021-10-10 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 13:31 [PATCH] test-lib.sh: try to re-chmod & retry on failed trash removal Ævar Arnfjörð Bjarmason
2021-10-10 21:36 ` SZEDER Gábor
2021-10-10 22:14 ` Junio C Hamano [this message]
2021-10-11 4:34 ` Junio C Hamano
2021-10-11 1:41 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2021-10-12 23:03 ` Junio C Hamano
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=xmqqee8seded.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.