From: Andre Loconte <andre.loconte@protonmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git bundle create produces inconsistent bundle
Date: Tue, 07 Jan 2020 17:44:47 +0000 [thread overview]
Message-ID: <QBxpUR_NauPk0G8X2KKsqzlrfyxNuA4OoNR3Dm1KpHMNEELiSUxKr_IDM_qghObDt4aVv-bjg1ZQtCYRgxArdGsK52wCuO1LbsqzlHBto-k=@protonmail.com> (raw)
Hello,
I am running into an issue where "git bundle create" doesn't always produce the same bundle, provided the exact same arguments and the exact same repo.
Where it gets tricky is that:
- I cannot reproduce the issue with random repos from Github (tried with ~10 repos and 30 bundles per repo);
- I cannot reproduce the issue with the same OS and git version on different hardware ;
- I can reproduce the issue on colleagues' workstation (environment is identical down to the hardware, see below).
Environment:
- GNU/Linux 5.3.0-24-generic Ubuntu 19.10 x86_64 ;
- git version 2.20.1 ;
- Intel Xeon Silver 4114 CPU @ 2.20GHz × 20 ;
- 4 × Hynix HMA81GR7CJR8N-VK 8GB DDR4-2666 ECC.
I have put together a bash PoC [1]. And there are some example output in the comments (consistent [2], inconsistent [3]).
[1] https://gist.github.com/alct/05cc9a2b4657d51669c96cb22cd5c4a6
[2] https://gist.github.com/alct/05cc9a2b4657d51669c96cb22cd5c4a6#gistcomment-3130206
[3] https://gist.github.com/alct/05cc9a2b4657d51669c96cb22cd5c4a6#gistcomment-3130213
I cannot share the affected repos but I can run any diagnostic tool against them.
Would you have any clue on what could produce such behavior?
Best,
A.L.
next reply other threads:[~2020-01-07 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:44 Andre Loconte [this message]
2020-01-07 18:03 ` Git bundle create produces inconsistent bundle Jeff King
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='QBxpUR_NauPk0G8X2KKsqzlrfyxNuA4OoNR3Dm1KpHMNEELiSUxKr_IDM_qghObDt4aVv-bjg1ZQtCYRgxArdGsK52wCuO1LbsqzlHBto-k=@protonmail.com' \
--to=andre.loconte@protonmail.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.
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).