From: Ayush Chandekar <ayu.chandekar@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 2/2] t5319: add test for MIDX QSORT progress reporting
Date: Mon, 10 Feb 2025 13:16:23 +0530 [thread overview]
Message-ID: <20250210074623.136599-3-ayu.chandekar@gmail.com> (raw)
In-Reply-To: <20250210074623.136599-1-ayu.chandekar@gmail.com>
Add a test to verify that the multi-pack-index verify command shows
progress during the QSORT operation. Create 100 test objects, repack
them, and verify the progress reaches 100% during sorting
Signed-off-by: Ayush Chandekar <ayu.chandekar@gmail.com>
---
This test makes sure the progress reaches 100%, but I couldn't find a way
which could verify that the progress went from 0% to 100% with intermediates.
I would like if someone can suggest a method for this.
Thanks,
Ayush
t/t5319-multi-pack-index.sh | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/t/t5319-multi-pack-index.sh b/t/t5319-multi-pack-index.sh
index 0f215ad2e8..d368e22e3a 100755
--- a/t/t5319-multi-pack-index.sh
+++ b/t/t5319-multi-pack-index.sh
@@ -658,6 +658,20 @@ test_expect_success 'verify incorrect 64-bit offset' '
"incorrect object offset"
'
+test_expect_success 'verify shows QSORT progress' '
+ # Create test objects
+ for i in $(test_seq 1 100)
+ do
+ echo "content $i" | \
+ git hash-object -w --stdin \
+ || return 1
+ done &&
+ git repack -ad &&
+ git multi-pack-index write &&
+ GIT_PROGRESS_DELAY=0 git multi-pack-index verify --progress 2>actual &&
+ grep "Sorting objects by packfile: *100%" actual
+'
+
test_expect_success 'setup expire tests' '
mkdir dup &&
(
--
2.48.GIT
prev parent reply other threads:[~2025-02-10 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:46 [GSOC][RFC PATCH 0/2] midx: implement progress reporting for QSORT operation Ayush Chandekar
2025-02-10 7:46 ` [PATCH 1/2] midx: show progress during " Ayush Chandekar
2025-02-10 16:55 ` Junio C Hamano
2025-02-11 12:23 ` Ayush Chandekar
2025-02-11 16:29 ` Junio C Hamano
2025-02-10 7:46 ` Ayush Chandekar [this message]
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=20250210074623.136599-3-ayu.chandekar@gmail.com \
--to=ayu.chandekar@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).