> @#11 I think that's the timeline I was describing too. I don't think
> it's ever more than 1 hour of actual useful work, is it?
Considerably more than 1 hour. IIRC it ran for about 5-6 hours before it
quit updating. And we did track it down to a single huge revision. During
the previous investigation, I pulled one revision at a time. I don't have
the revision #.
> Then there's one hour stuck,
Or one hour spent fussing with that one huge revision. I believe that this
is also documented -- these is a description of what it's doing during that
time.
> then that phase is terminating by the whole program erroring.
>
And then it gets disconnected at the launchpad end. The local bzr just
reports that.
> @#11 I think that's the timeline I was describing too. I don't think
> it's ever more than 1 hour of actual useful work, is it?
Considerably more than 1 hour. IIRC it ran for about 5-6 hours before it
quit updating. And we did track it down to a single huge revision. During
the previous investigation, I pulled one revision at a time. I don't have
the revision #.
> Then there's one hour stuck,
Or one hour spent fussing with that one huge revision. I believe that this
is also documented -- these is a description of what it's doing during that
time.
> then that phase is terminating by the whole program erroring.
>
And then it gets disconnected at the launchpad end. The local bzr just
reports that.
-- Pat