all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: "bzr commit" takes 17 minutes?
Date: Fri, 25 Feb 2011 13:23:01 +0200	[thread overview]
Message-ID: <83fwrcqrxm.fsf@gnu.org> (raw)
In-Reply-To: <83mxlkqsq6.fsf@gnu.org>

> Date: Fri, 25 Feb 2011 13:05:53 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> Not that long, never.  A commit is typically 1-2 min for me.  Which is
> also slow, but not as bad as 17 min.  Is the above time exceptional,
> or do you get that as a matter of routine?  You can gather statistics
> from your ~/.bzr.log file.

Something _is_ strange with bzr.savanna.gnu.org.  It just took me a
full minute to get a single revision with "bzr up", something that
should take 20 sec at most.  And "bzr up" in the emacs-23 branch took
2.5 minutes(!).

It worked fine just a couple of hours ago.

I'll ask on Savannah-hackers-public about this.



  reply	other threads:[~2011-02-25 11:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 10:24 "bzr commit" takes 17 minutes? Paul Eggert
2011-02-25 10:47 ` Andreas Schwab
2011-02-25 11:08   ` Eli Zaretskii
2011-02-25 11:05 ` Eli Zaretskii
2011-02-25 11:23   ` Eli Zaretskii [this message]
2011-02-25 11:51     ` Eli Zaretskii
2011-02-25 12:01       ` Eli Zaretskii
2011-02-25 17:46         ` Glenn Morris
2011-02-26  4:30           ` Miles Bader
2011-02-25 18:30         ` Savannah slowdown due to cgit.cgi [was Re: "bzr commit" takes 17 minutes?] Glenn Morris
2011-02-26  0:45           ` Andrew W. Nosenko
2011-02-26  7:10             ` Eli Zaretskii
2011-02-25 17:41       ` "bzr commit" takes 17 minutes? Thierry Volpiatto
2011-02-25 17:59         ` Eli Zaretskii
2011-02-25 18:13           ` Thierry Volpiatto
2011-02-25 18:55             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83fwrcqrxm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.