diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2022-07-29 12:28:43 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2022-07-29 09:08:57 -0700 |
commit | ce50f1f3ac9c2e053b1b4644587be8ef1f69af88 (patch) | |
tree | 6d708fc6e0f594966d4ed30e6abaf6d55ed8522e /commit.c | |
parent | 23b219f8e3f2adfb0441e135f0a880e6124f766c (diff) |
t5351: avoid relying on `core.fsyncMethod = batch` to be supported
On FreeBSD, this mode is not supported. But since 3a251bac0d1a (trace2:
only include "fsync" events if we git_fsync(), 2022-07-18) t5351 will
fail if this mode is unsupported.
Let's address this in the minimal fashion, by detecting that that mode
is unsupported and expecting a different count of hardware flushes in
that case.
This fixes the CI/PR builds on FreeBSD again.
Note: A better way would be to test only what is relevant in t5351.6
"unpack big object in stream (core.fsyncmethod=batch)" again instead of
blindly comparing the output against some exact text. But that would
pretty much revert the idea of above-mentioned commit, and that commit
was _just_ accepted into Git's main branch so one must assume that it
was intentional.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions