convert exception with django trunk

[Faheem Mitha]

On Sun, 25 May 2008 22:44:09 +0300, Dov Feldstern
<dfeldstern at fastimap.com> wrote:

> Faheem Mitha wrote:
>> On Fri, 23 May 2008 14:34:45 -0400 (EDT), Faheem Mitha
>> <faheem at email.unc.edu> wrote:
>> 
>>> Hi,
>>>
>>> This is with Django trunk (r7546). Should I file an issue? Please cc me on 
>>> any reply.
>> 
>> The convert is successful with 1.0.1, though it takes forever to
>> complete. So, please disregard this issue.
>
> How long is "forever"? I know that when I try converting from LyX, it does not 
> complete after even an hour or so... I just opened an issue about this a few 
> days ago (http://www.selenic.com/mercurial/bts/issue1133).

I didn't really keep track, but my impression is most of a
day. Anything from 8 to 12 hours, though probably at the lower end of
that.

> IMO, it should *not* be disregarded: I used to track the LyX svn
> repository by converting every 30 minutes with a cron job. However,
> this is now impossible: first of all, running an hour-long job every
> half-hour just doesn't make sense; and secondly, the job was timing
> out before completing successfully. So I really do think that
> something should be done about this, and I'm happy to hear
> confirmation of this problem from another source...

hg convert didn't abort during this time, so I didn't need to restart
it at all. However, the machine I'm running it on has 4 Gig. I didn't
check to see how much memory is was using. Some reports suggest that
hg convert has a memory leak, which wouldn't help if true.

In summary, I didn't see a problem with this particular conversion,
but obviously it would be nice if it completed faster.

It might be possible to do the convert incrementally. The current hg
mirror of django uses hg convert I think, and it is unlikely that he
is doing it from scratch every time. You could ask him - or someone
here might have an idea.
                                                            Faheem.