June, 09 at 19:50 Glenn wrote:
(It would have been helpful to have the start of this discussion referenced:
http://lists.gnu.org/archive/html/emacs-devel/2013-06/msg00236.html )
Sorry I didn't. I was following Eli's suggestion.
Maybe Ivan was doing an anonymous checkout?
I don't think so.
Ivan Kanis wrote:
Sorry I didn't. I was following Eli's suggestion.
I did suggest only doing that next time. There's not much point moving a
conversation that's already in progress. Anyway, let's carry on now.
I think that is the problem. My desktop is somewhat slow compared to
modern
PS Karl, should I write down somewhere what I think I understand about
how this is set up on Savannah? There's a wiki somewhere?
June, 10 at 3:11 Glenn wrote:
Could you tell us what actually happens?
I get the timeout error.
How long does the bzr process run for?
The process bzr does not end, ie. I do not get my prompt back.
Is it doing anything when it dies, or has it been idle for 5 mins?
After 40 minutes, the
We can in principle increase the 300s timeout by passing
--client-timeout=ARG to bzr serve in /usr/local/bin/sv_membersh,
I think we should (to, say, an hour), regardless of whether that helps
Ivan or not, because all experience is that networks fail in
unpredictable and unknowable ways.
PS Karl, should I write down somewhere what I think I understand about
how this is set up on Savannah?
Yes please. For now, can you just post it here as an email message and I will
endeavor to save it for later updating?
There's a wiki somewhere?
The wiki is frozen right now.
5 hours isn't enough? Ok, I changed the timeout I know about to 10.
I don't think you needed to change that.
I think you're right :). I switched it back to 5 hours.
Thanks,
k
Karl Berry wrote:
We can in principle increase the 300s timeout by passing
--client-timeout=ARG to bzr serve in /usr/local/bin/sv_membersh,
I think we should (to, say, an hour), regardless of whether that helps
Ivan or not, because all experience is that networks fail in
Karl Berry wrote:
Agreed. Let's try removing it and see if there is some immediate
failure report?
Ah, the scientific method. :)
Done.
