WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] hg pull: out-of-memory errors? ("abort: group to be adde

To: Hollis Blanchard <hollisb@xxxxxxxxxx>
Subject: Re: [Xen-devel] hg pull: out-of-memory errors? ("abort: group to be added is empty!")
From: Bryan O'Sullivan <bos@xxxxxxxxxxxxxx>
Date: Wed, 19 Apr 2006 12:10:50 -0700
Cc: James Bulpin <james@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 19 Apr 2006 12:10:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1145473446.9435.37.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1145473446.9435.37.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2006-04-19 at 14:04 -0500, Hollis Blanchard wrote:

> Could you check the xenbits server logs to see if there are hg processes
> being killed, possibly because of out-of-memory conditions? Thanks...

It may also be worth upgrading the server to the current tip version of
Mercurial, once that has seen some more testing.  Matt just merged some
changes written by Chris Mason that reduce disk and memory usage
substantially, which should reduce the squeeze that the xenbits server
gets put under.

I'll see what we can do to print a more useful error message when the
xenbits server gets killed, as it's quite a common problem.

        <b

-- 
Bryan O'Sullivan <bos@xxxxxxxxxxxxxx>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>