problem merging from bzr

problem merging from bzr

[joakim]

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.

-- 
Joakim Verona

Re: problem merging from bzr

[Eli Zaretskii]

> 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).

Re: problem merging from bzr

[joakim]

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

Re: problem merging from bzr

[Eli Zaretskii]

> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Wed, 18 Apr 2012 19:04:18 +0200
> 
> >> 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

I guess you should report this to the Bazaar list, if not file a bug
report.  (I would start with the list, since they could offer some
workaround or maybe some secret switch to get more detailed debug info
that would explain why this happens.)

Re: problem merging from bzr

[Eli Zaretskii]

> Date: Wed, 18 Apr 2012 20:12:05 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > In dmesg:
> > [140591.887966] Out of memory: Kill process 1898 (bzr) score 642 or sacrifice child

Btw, since OOM doesn't necessarily kill the process that caused the
out-of-memory condition, it would be good to watch the memory
consumption while "bzr merge" works, to make sure it is it that's the
culprit (although it sounds very likely from your description).