From: Tamir Duberstein <tamird@gmail.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>,
Junio C Hamano <gitster@pobox.com>,
Tamir Duberstein <tamird@gmail.com>
Subject: [PATCH 1/2] t4205: compare huge output without diff
Date: Wed, 23 Sep 2026 13:13:28 -0400 [thread overview]
Message-ID: <20260923-ci-large-test-resources-v1-1-c28416d59475@gmail.com> (raw)
In-Reply-To: <20260923-ci-large-test-resources-v1-0-c28416d59475@gmail.com>
The huge-commit test compares two files with a line larger than 2 GiB.
In Linux GitHub Actions jobs, git log produces its huge output but
its subsequent diff process is killed with SIGKILL.
Use test_cmp_bin to compare the output byte for byte without constructing
a line-oriented diff. Remove the two large files after a successful
comparison, releasing more than 4 GiB before subsequent tests.
Signed-off-by: Tamir Duberstein <tamird@gmail.com>
---
t/t4205-log-pretty-formats.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/t/t4205-log-pretty-formats.sh b/t/t4205-log-pretty-formats.sh
index 4be5c51489..6279a7e9bc 100755
--- a/t/t4205-log-pretty-formats.sh
+++ b/t/t4205-log-pretty-formats.sh
@@ -1189,7 +1189,8 @@ test_expect_success EXPENSIVE,SIZE_T_IS_64BIT 'set up huge commit' '
test_expect_success EXPENSIVE,SIZE_T_IS_64BIT 'log --pretty with huge commit message' '
git log -1 --format="%B%<(1)%x30" $huge_commit >actual &&
echo 0 >>expect &&
- test_cmp expect actual
+ test_cmp_bin expect actual &&
+ rm expect actual
'
test_expect_success EXPENSIVE,SIZE_T_IS_64BIT 'log --pretty with huge commit message does not cause allocation failure' '
--
2.56.0.rc0.807.ga0c0929ce1.frankengit
next prev parent reply other threads:[~2026-09-23 17:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 17:13 [PATCH 0/2] ci: reduce pressure from large test fixtures Tamir Duberstein
2026-09-23 17:13 ` Tamir Duberstein [this message]
2026-09-24 6:13 ` [PATCH 1/2] t4205: compare huge output without diff Patrick Steinhardt
2026-09-24 20:41 ` Tamir Duberstein
2026-09-25 0:13 ` Jeff King
2026-09-25 6:41 ` Junio C Hamano
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-23 17:13 ` [PATCH 2/2] ci: match Linux jobs to available CPUs Tamir Duberstein
2026-09-24 6:13 ` Patrick Steinhardt
2026-09-25 15:03 ` Tamir Duberstein
2026-09-23 18:36 ` [PATCH 0/2] ci: reduce pressure from large test fixtures Tamir Duberstein
2026-09-25 16:35 ` [PATCH v2 0/2] ci: use cmp and align job-count selection Tamir Duberstein
2026-09-25 16:35 ` [PATCH v2 1/2] t4205: compare huge output without diff Tamir Duberstein
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-25 16:35 ` [PATCH v2 2/2] ci: align job counts across CI providers Tamir Duberstein
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-28 10:16 ` Tamir Duberstein
2026-09-28 11:14 ` Patrick Steinhardt
2026-09-30 14:20 ` [PATCH v3 0/2] ci: use cmp and align job-count selection Tamir Duberstein
2026-09-30 14:20 ` [PATCH v3 1/2] t4205: compare huge output without diff Tamir Duberstein
2026-09-30 14:20 ` [PATCH v3 2/2] ci: use twice the CPU count on both providers Tamir Duberstein
2026-09-30 14:45 ` Patrick Steinhardt
2026-09-30 14:45 ` [PATCH v3 0/2] ci: use cmp and align job-count selection Patrick Steinhardt
2026-09-30 14:58 ` Tamir Duberstein
2026-09-30 18:04 ` 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=20260923-ci-large-test-resources-v1-1-c28416d59475@gmail.com \
--to=tamird@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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