From: joakim@verona.se
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: problem merging from bzr
Date: Wed, 18 Apr 2012 19:04:18 +0200 [thread overview]
Message-ID: <m3liltezu5.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <83mx696lki.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 Apr 2012 19:39:41 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: joakim@verona.se
>> Date: Wed, 18 Apr 2012 12:25:27 +0200
>>
>> I get this weird behaviour all af a sudden:
>>
>> bzr merge
>>
>> Merging from remembered submit location bzr+ssh://jave@bzr.savannah.gnu.org/emacs/trunk/
>> Killedhing revisions:Inserting stream:repacking texts:texts 26866/48438
>>
>> Notice the "Killed" message in there. This is when I try to merge my
>> "xwidgets" branch from upstream.
>
> Could be OOM (out-of-memory) kill by the OS. Look for relevant
> messages in /var/log/messages (assuming this is GNU/Linux).
In dmesg:
[140591.887966] Out of memory: Kill process 1898 (bzr) score 642 or sacrifice child
Interesting.
Some more statistics, since I seem to have forgot that in my last mail:
Fedora 17 Beta (So could be the culprit of course, but its stable otherwise)
Bazaar (bzr) 2.5.0
Python interpreter: /usr/bin/python 2.7.3
Python standard library: /usr/lib64/python2.7
Platform: Linux-3.3.1-5.fc17.x86_64-x86_64-with-fedora-17-Beefy_Miracle
bzrlib: /usr/lib64/python2.7/site-packages/bzrlib
Bazaar configuration: /home/joakim/.bazaar
Bazaar log file: /home/joakim/.bzr.log
(I upgraded to get this version and co-located branches)
The machine is a Core i7, 6GB ram
--
Joakim Verona
next prev parent reply other threads:[~2012-04-18 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 10:25 problem merging from bzr joakim
2012-04-18 16:39 ` Eli Zaretskii
2012-04-18 17:04 ` joakim [this message]
2012-04-18 17:12 ` Eli Zaretskii
2012-04-18 17:42 ` 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=m3liltezu5.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=eliz@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 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.