Comment 11 for bug 537116
Revision history for this message
| Pat Tressel (ptressel) wrote Re: [Bug 537116] Re: bzr branch from launchpad disconnected after exactly one hour | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Mon, Sep 27, 2010 at 8:56 PM, Martin Pool <email address hidden> wrote:
> One contributing factor here is that the branch
> lp:~mdipierro/web2py/devel is in an old bzr format and it will be faster
> for all involved if the owner upgrades it.
>
> To summarize, there are three phases:
>
> 0-60m bzr slowly pulls stuff
> 60-120m bzr apparently stuck doing nothing
> 120m server disconnects the client
>
> It's not surprising that the client's disconnected after an hour of
> inactivity; in fact that's a feature.
>
> The real problem is that we hang
> for an hour before that. It would be highly useful to get a traceback
> during that phase.
>
That's not what I understood from the investigation that has already been
done, but I could be wrong... It sounds as though there is *no* period of
inactivity. There are *not* two separate one hour intervals involved.
Rather, the bzr activity that is going on is not regarded as activity by
launchpad. During the one hour of what launchpad regards as inactivity, bzr
is busy doing something relating to a single enormous revision, which is
possibly a collection of a large number of merged revisions.
So rather than three phases:
0 to N hours: bzr is visibly making progress.
N to N+1 hours: bzr stops visibly making progress.
N+1 hour: bzr exits with error.
-- Pat