From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <e@80x24.org>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] tests: disable fsync everywhere
Date: Thu, 28 Oct 2021 22:18:24 -0700 [thread overview]
Message-ID: <xmqqr1c4mmsf.fsf@gitster.g> (raw)
In-Reply-To: <20211029001552.GA29647@dcvr> (Eric Wong's message of "Fri, 29 Oct 2021 00:15:52 +0000")
Eric Wong <e@80x24.org> writes:
> @@ -42,6 +42,7 @@ const char *git_hooks_path;
> int zlib_compression_level = Z_BEST_SPEED;
> int pack_compression_level = Z_DEFAULT_COMPRESSION;
> int fsync_object_files;
> +int use_fsync = -1;
OK, (-1) is "undetermined yet", as usual.
> diff --git a/git-cvsserver.perl b/git-cvsserver.perl
> index 64319bed43..4c8118010a 100755
> --- a/git-cvsserver.perl
> +++ b/git-cvsserver.perl
> @@ -3607,6 +3607,22 @@ package GITCVS::updater;
> use strict;
> use warnings;
> use DBI;
> +our $_use_fsync;
> +
> +# n.b. consider using Git.pm
> +sub use_fsync {
> + if (!defined($_use_fsync)) {
> + my $x = $ENV{GIT_TEST_FSYNC};
> + if (defined $x) {
I would have expected to see "exists $ENV{GIT_TEST_FSYNC}", but I
guess there is no way to place in %ENV anyway, so it would be OK.
> + local $ENV{GIT_CONFIG};
> + delete $ENV{GIT_CONFIG};
OK, "git -c test.fsync=no cvsserver" would added something to
GIT_CONFIG that would affect test.fsync, but wouldn't the usual
last-one-wins rule be sufficient to check the value of $x using the
next construction, no matter what is in GIT_CONFIG? I do not think
it would hurt to delete $ENV{GIT_CONFIG}, but I am not sure how it
is necessary.
> + my $v = ::safe_pipe_capture('git', '-c', "test.fsync=$x",
> + qw(config --type=bool test.fsync));
THis is an interesting idiom.
> + $_use_fsync = defined($v) ? ($v eq "true\n") : 1;
> + }
> + }
> + $_use_fsync;
> +}
> +# TODO: move this to Git.pm?
> +sub use_fsync {
Possibly, but in a slightly more general form, taking the name of
the environment variable that holds a boolean value as an argument,
or something?
> diff --git a/t/test-lib.sh b/t/test-lib.sh
> index a291a5d4a2..21f5fab999 100644
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -489,6 +489,13 @@ then
> export GIT_PERL_FATAL_WARNINGS
> fi
>
> +case $GIT_TEST_FSYNC in
> +'')
> + GIT_TEST_FSYNC=0
> + export GIT_TEST_FSYNC
> + ;;
> +esac
> diff --git a/write-or-die.c b/write-or-die.c
> index 0b1ec8190b..a3d5784cec 100644
> --- a/write-or-die.c
> +++ b/write-or-die.c
> @@ -1,4 +1,5 @@
> #include "cache.h"
> +#include "config.h"
> #include "run-command.h"
>
> /*
> @@ -57,6 +58,10 @@ void fprintf_or_die(FILE *f, const char *fmt, ...)
>
> void fsync_or_die(int fd, const char *msg)
> {
> + if (use_fsync < 0)
> + use_fsync = git_env_bool("GIT_TEST_FSYNC", 1);
> + if (!use_fsync)
> + return;
OK. That's quite straight-forward.
> while (fsync(fd) < 0) {
> if (errno != EINTR)
> die_errno("fsync error on '%s'", msg);
Will queue.
next prev parent reply other threads:[~2021-10-29 5:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 0:21 [PATCH] allow disabling fsync everywhere Eric Wong
2021-10-28 1:21 ` Eric Sunshine
2021-10-28 14:36 ` Jeff King
2021-10-28 18:28 ` Eric Wong
2021-10-28 19:29 ` Junio C Hamano
2021-10-29 0:15 ` [PATCH] tests: disable " Eric Wong
2021-10-29 5:18 ` Junio C Hamano [this message]
2021-10-29 7:56 ` Eric Wong
2021-10-29 18:12 ` Junio C Hamano
2021-10-29 7:33 ` Junio C Hamano
2021-10-29 7:48 ` Eric Wong
2021-10-29 17:22 ` Junio C Hamano
2021-10-29 20:34 ` Jeff King
2021-10-29 20:42 ` Junio C Hamano
2021-10-28 21:40 ` [PATCH] allow disabling " brian m. carlson
2021-10-29 11:20 ` Ævar Arnfjörð Bjarmason
2021-10-30 10:39 ` Eric Wong
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=xmqqr1c4mmsf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).