From: Abhra303 <chakrabortyabhradeep79@gmail.com>
To: Git <git@vger.kernel.org>
Cc: "Abhradeep Chakraborty" <chakrabortyabhradeep79@gmail.com>,
"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Derrick Stolee" <derrickstolee@github.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Fixing midx bitmap related racy test failure (under sha-256)
Date: Mon, 15 Aug 2022 12:34:46 +0530 [thread overview]
Message-ID: <20220815070446.4990-1-chakrabortyabhradeep79@gmail.com> (raw)
From: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Hello developers,
I have been writing a patch series[1] to integrate a lookup table extension
to .bitmap file. I reformatted the test code so that I can run the same
tests for the lookup table extension. But this is causing a failure in a midx
bitmap related test case[2]. It is not related to my code because this
can be produced with out my changes.
If you see the test file[3] (with my changes) and also observe the test
results[4], you'll notice that the said test case is always failing on the
second `test_midx_bitmap_cases` call under sha-256 only. This is racy in nature.
I.e. it might pass after executing the test 2 or 3 times.
I have been trying to solve the issue for one or two week but as I am not
very clear about the internal working of multi-pack-index or repacking, I
am still not able to solve the issue. Besides, my semester exam is starting
from 18 Aug. So I have to give a significant amount of time to studies.
So, it will be very helpful if anyone help me to find out the solution.
You can know more from this thread[5].
Thanks :)
[1] https://lore.kernel.org/git/pull.1266.git.1655728395.gitgitgadget@gmail.com/
[2] https://github.com/Abhra303/git/blob/b460516b306e6885cd1c0af1c3379fb953952de2/t/lib-bitmap.sh#L195
[3] https://github.com/Abhra303/git/blob/bitmap-commit-table/t/t5326-multi-pack-bitmaps.sh
[4] https://github.com/Abhra303/git/runs/7827604510?check_suite_focus=true
[5] https://lore.kernel.org/git/p3r70610-8n52-s8q0-n641-onp4ps01330n@tzk.qr/#t
reply other threads:[~2022-08-15 7:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220815070446.4990-1-chakrabortyabhradeep79@gmail.com \
--to=chakrabortyabhradeep79@gmail.com \
--cc=avarab@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).