From: James Bulpin <james@xensource.com>
To: Bryan O'Sullivan <bos@serpentine.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: hg pull: out-of-memory errors? ("abort: group to be added is empty!")
Date: Wed, 19 Apr 2006 21:25:47 +0100 [thread overview]
Message-ID: <44469CCB.5020803@xensource.com> (raw)
In-Reply-To: <1145473850.21283.16.camel@localhost.localdomain>
There is nothing untoward in any log as far as I can see. The oom killer
hasn't come out to play either.
Anyway, xenbits is now running 0.8.1, I'll upgrade as Bryan suggests
once a new version is called.
We've had 0.8.1 testing on an internal server for a few days so I have
confidence the upgrade should be safe. As ever, do let me know if any
problems are seen.
Note that the temporary server that the 3.0-testing tree is redirected
to is still running 0.7 but will disappear shortly once I move the
hosting to our new colo centre.
Regards,
James
Bryan O'Sullivan wrote:
> 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
>
prev parent reply other threads:[~2006-04-19 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 19:04 hg pull: out-of-memory errors? ("abort: group to be added is empty!") Hollis Blanchard
2006-04-19 19:10 ` Bryan O'Sullivan
2006-04-19 20:25 ` James Bulpin [this message]
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=44469CCB.5020803@xensource.com \
--to=james@xensource.com \
--cc=bos@serpentine.com \
--cc=hollisb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.
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.