From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Douglas Mencken <dougmencken@gmail.com>, git@vger.kernel.org
Subject: Re: [regression] Newer gits cannot clone any remote repos
Date: Thu, 15 Nov 2012 19:17:00 +0000 [thread overview]
Message-ID: <50A53FAC.8020401@ramsay1.demon.co.uk> (raw)
In-Reply-To: <50A2B2DF.1080704@web.de>
Torsten Bögershausen wrote:
> On 13.11.12 19:55, Ramsay Jones wrote:
>> Douglas Mencken wrote:
>>> *Any* git clone fails with:
>>>
>>> fatal: premature end of pack file, 106 bytes missing
>>> fatal: index-pack failed
>>>
>>> At first, I tried 1.8.0, and it failed. Then I tried to build 1.7.10.5
>>> then, and it worked. Then I tried 1.7.12.2, but it fails the same way
>>> as 1.8.0.
>>> So I decided to git bisect.
>>>
>>> b8a2486f1524947f232f657e9f2ebf44e3e7a243 is the first bad commit
>>> ``index-pack: support multithreaded delta resolving''
>>
>> This looks like the same problem I had on cygwin, which lead to
>> commit c0f86547c ("index-pack: Disable threading on cygwin", 26-06-2012).
>>
>> I didn't notice which platform you are on, but maybe you also have a
>> thread-unsafe pread()? Could you try re-building git with the
>> NO_THREAD_SAFE_PREAD build variable set?
>>
>> HTH.
>>
>> ATB,
>> Ramsay Jones
>
> This is interesting.
> I had the same problem on a PowerPC
> (Old PowerBook G4 running Linux).
>
> Using NO_THREAD_SAFE_PREAD helped, thanks for the hint.
> (After recompiling without NO_THREAD_SAFE_PREAD I could clone
> from this machine again, so the problem is not really reproducable)
Yes, the failures would be intermittent (and often not easily
reproducible). The threaded index-pack code did not fail for
me on cygwin at all during development, including tests, but failed
immediately I installed v1.7.11. On real repositories, it failed
intermittently. On some repos it always failed, on some it never
failed and on some others it would sometimes fail, sometimes not.
ATB,
Ramsay Jones
next prev parent reply other threads:[~2012-11-15 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 16:32 [regression] Newer gits cannot clone any remote repos Douglas Mencken
2012-11-12 17:12 ` Kevin
2012-11-12 19:35 ` Douglas Mencken
[not found] ` <CAO54GHA=r8WUK3okm2imVkoB=SuZ=3o+wwdwLr_rmPXhdFzG_g@mail.gmail.com>
2012-11-12 17:13 ` Douglas Mencken
2012-11-13 18:55 ` Ramsay Jones
2012-11-13 19:55 ` Douglas Mencken
2012-11-13 20:33 ` Douglas Mencken
2012-11-15 12:51 ` Nguyen Thai Ngoc Duy
2012-11-15 18:55 ` Ramsay Jones
2012-11-13 20:51 ` Torsten Bögershausen
2012-11-13 22:36 ` Andreas Schwab
2012-11-14 16:19 ` Douglas Mencken
2012-11-14 16:32 ` Andreas Schwab
2012-11-14 18:01 ` Douglas Mencken
2012-11-14 23:15 ` Andreas Schwab
2012-11-15 19:17 ` Ramsay Jones [this message]
2012-11-21 19:20 ` Douglas Mencken
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=50A53FAC.8020401@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=dougmencken@gmail.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.