Comment 14 for bug 537116

@#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? Then there's one hour stuck, then that phase is terminating by the whole program erroring.

I just tested this with an additional 1000ms latency on eth0, and it completed in 43m, probably not enough to provoke whatever's happening at the 1h mark. I would have thought that if there was something CPU-bound that caused a long hang, it would show up in this. This branching used only 36s cpu time locally, so it seems unlikely that could blow out to 1h of work unless your machine is much slower. It may be you have some kind of environment where things do become much worse.

Do you now have a working branch or are you still blocked?