From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 2/6] test_common: disable fsync in git(1) commands
Date: Fri, 15 Nov 2024 02:59:28 +0000 [thread overview]
Message-ID: <20241115025932.1647240-3-e@80x24.org> (raw)
In-Reply-To: <20241115025932.1647240-1-e@80x24.org>
As with git itself, fsync(2) results in needless overhead and
storage wear in test cases where data integrity is not an issue.
I normally point TMPDIR to tmpfs when running tests, but this
still affects initial setup of data for stuff in t/data-gen as
well as improving life for users with too little RAM for a tmpfs
TMPDIR.
---
lib/PublicInbox/TestCommon.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/PublicInbox/TestCommon.pm b/lib/PublicInbox/TestCommon.pm
index 6c3677d2..b863ad6b 100644
--- a/lib/PublicInbox/TestCommon.pm
+++ b/lib/PublicInbox/TestCommon.pm
@@ -18,6 +18,7 @@ our $tail_cmd = $ENV{TAIL};
our ($lei_opt, $lei_out, $lei_err);
use autodie qw(chdir close fcntl mkdir open opendir seek unlink);
$ENV{XDG_CACHE_HOME} //= "$ENV{HOME}/.cache"; # reuse C++ xap_helper builds
+$ENV{GIT_TEST_FSYNC} = 0; # hopefully reduce wear
$_ = File::Spec->rel2abs($_) for (grep(!m!^/!, @INC));
our $CURRENT_DAEMON;
@@ -87,6 +88,7 @@ sub tmpdir (;$) {
my ($base) = @_;
require File::Temp;
($base) = ($0 =~ m!\b([^/]+)\.[^\.]+\z!) unless defined $base;
+ ($base) = ($0 =~ m!\b([^/]+)\z!) unless defined $base;
my $tmpdir = File::Temp->newdir("pi-$base-$$-XXXX", TMPDIR => 1);
wantarray ? ($tmpdir->dirname, $tmpdir) : $tmpdir;
}
next prev parent reply other threads:[~2024-11-15 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 2:59 [PATCH 0/6] a few random small fixes and improvements Eric Wong
2024-11-15 2:59 ` [PATCH 1/6] tests: fix missing modules under TEST_RUN_MODE=0 Eric Wong
2024-11-15 2:59 ` Eric Wong [this message]
2024-11-15 2:59 ` [PATCH 3/6] nntp: improve protocol error messages Eric Wong
2024-11-15 2:59 ` [PATCH 4/6] nntp: integerize {article} to save memory Eric Wong
2024-11-15 2:59 ` [PATCH 5/6] view: reduce ops for <b> encasement Eric Wong
2024-11-15 2:59 ` [PATCH 6/6] view: fix obfuscation in message/* attachments 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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241115025932.1647240-3-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).