From: Paul Eggert <eggert@cs.ucla.edu>
To: Emacs Development <emacs-devel@gnu.org>
Cc: Savannah-hackers-public@gnu.org
Subject: bzr + savannah.gnu.org slow again
Date: Fri, 25 Feb 2011 22:21:33 -0800 [thread overview]
Message-ID: <4D689BED.5020908@cs.ucla.edu> (raw)
Savannah.gnu.org is very slow for bzr commits on the Emacs trunk,
with symptoms much like they were about 24 hours ago. Perhaps the
same thing is happening again?
My most recent attempt to commit is taking more than 20 minutes.
It's not done yet, so I don't know how long it will take exactly.
Here are the symptoms at the shell level:
$ bzr commit -m 'Merge: lib-src changes mostly to avoid GCC warnings'
Committing to: bzr+ssh://eggert@bzr.savannah.gnu.org/emacs/trunk/
modified lib-src/ChangeLog
modified lib-src/ebrowse.c
modified lib-src/emacsclient.c
modified lib-src/etags.c
modified lib-src/fakemail.c
modified lib-src/make-docfile.c
[ It's hanging here now. ]
Here is my ~/.bzr.log:
Fri 2011-02-25 21:53:48 -0800
0.073 bazaar version: 2.2.2
0.073 bzr arguments: [u'commit', u'-m', u'Merge: lib-src changes mostly to avoid GCC warnings']
0.096 looking for plugins in /u/cs/fac/eggert/.bazaar/plugins
0.096 looking for plugins in /usr/local/cs/Python-2.6.6/lib/python2.6/site-packages/bzrlib/plugins
0.117 encoding stdout as sys.stdout encoding 'UTF-8'
0.245 opening working tree '/w/fac.2/cs/eggert/src/gnu/emacs/trunk'
0.566 ssh implementation is OpenSSH
38.887 preparing to commit
[10929] 2011-02-25 21:54:36.575 INFO: Committing to: bzr+ssh://eggert@bzr.savannah.gnu.org/emacs/trunk/
47.711 Selecting files for commit with filter None
[10929] 2011-02-25 21:54:37.032 INFO: modified lib-src/ChangeLog
[10929] 2011-02-25 21:54:37.033 INFO: modified lib-src/ebrowse.c
[10929] 2011-02-25 21:54:37.033 INFO: modified lib-src/emacsclient.c
[10929] 2011-02-25 21:54:37.033 INFO: modified lib-src/etags.c
[10929] 2011-02-25 21:54:37.034 INFO: modified lib-src/fakemail.c
[10929] 2011-02-25 21:54:37.034 INFO: modified lib-src/make-docfile.c
48.761 Using fetch logic to copy between CHKInventoryRepository('file:///w/fac.2/cs/eggert/src/gnu/emacs/.bzr/repository/')(RepositoryFormat2a()) and RemoteRepository(bzr+ssh://eggert@bzr.savannah.gnu.org/emacs/.bzr/)(RemoteRepositoryFormat(_network_name='Bazaar repository format 2a (needs bzr 1.16 or later)\n'))
48.761 fetch up to rev {eggert@cs.ucla.edu-20110226055436-mfvjfrh702e68yqk}
142.288 stripping trailing bytes from groupcompress block 627289 => 258611
It is now Fri Feb 25 22:20:20 PST 2011, so it's about
27 minutes and counting.
next reply other threads:[~2011-02-26 6:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 6:21 Paul Eggert [this message]
2011-02-26 6:50 ` bzr + savannah.gnu.org slow again Paul Eggert
2011-02-26 7:54 ` Eli Zaretskii
2011-02-26 8:13 ` [Savannah-hackers-public] " Jim Meyering
2011-02-26 8:49 ` Eli Zaretskii
2011-02-26 9:06 ` Eli Zaretskii
2011-02-28 8:03 ` Glenn Morris
2011-02-28 13:02 ` Jim Meyering
2011-02-28 17:54 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D689BED.5020908@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Savannah-hackers-public@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).