out of memory, rollback not good?

Steve Borho steve at borho.org
Wed Jul 13 01:05:32 CDT 2011


On Wed, Jul 13, 2011 at 12:49 AM, rupert.thurner
<rupert.thurner at gmail.com> wrote:
> because somebody posted on the users mailing list that cloning the gcc
> ssh repository is impossible as it gets an error, i was curios and i
> tried.
>
> hg clone svn://gcc.gnu.org/svn/gcc/trunk gcc
> ...
> [r143562] dodji: Reverted commit 143546 related to PR c++/26693
> transaction abort!
> rollback completed
> abort: out of memory
>
> besides that mercurial is fife times slower than git in that case, it
> gets an out of memory error. and, there is no leftover "gcc" folder,
> which i thought is there until the revision 143562. which would allow
> to continue with a pull until the next error.
>
> the concerning diff is not especially big:
> svn diff -r143560:143562 http://gcc.gnu.org/svn/gcc/trunk
>
> what is so special with this clone that there is no leftover to
> continue?

The Python-SVN bindings have bad memory leaks in them.  Never try to
convert a large SVN repository in one command.

% hg clone -r 1 svn://gcc.gnu.org/svn/gcc/trunk gcc
% cd gcc ; hg pull

-- 
Steve Borho


More information about the Mercurial-devel mailing list