All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin.df@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [xen-unstable test] 13944: regressions - FAIL
Date: Wed, 10 Oct 2012 16:14:43 +0100	[thread overview]
Message-ID: <1349882083.3610.219.camel@Abyss> (raw)
In-Reply-To: <20596.26200.30125.482942@mariner.uk.xensource.com>

On Tue, 2012-10-09 at 19:00 +0100, Ian Jackson wrote: 
> This is this:
> 
> fatal: Out of memory? mmap failed: Cannot allocate memory
> fatal: The remote end hung up unexpectedly
> make[1]: *** [qemu-xen-dir-find] Error 128
> 
> On gall-mite:
> 
> root@gall-mite:~# free -m
>              total       used       free     shared    buffers     cached
> Mem:          8102       2059       6042          0        650       1286
> -/+ buffers/cache:        122       7980
> Swap:        12143          0      12143
> root@gall-mite:~# 
> 
> So it has 8G of RAM and 12G of swap.
> 
> I wonder if the git object cache is too big.  I will clear gall-mite's
> and see if it helps.
> 
Mmm, gall-mite is the box on which _all_ the sched=sedf test were
running for quite a bit of flights, and consistently failing at the
xen-boot stage. I pointed out the situation already here:

http://www.gossamer-threads.com/lists/xen/devel/258909?do=post_view_threaded

Now that the very same test has moved to some other host it seems to be
working again:

http://www.chiark.greenend.org.uk/~xensrcts/logs/13943/test-amd64-amd64-xl-sedf/info.html

That could be something very silly to think (in which case sorry), but
might this all be some hardware issue on that machine?

Regards,
Dario

  reply	other threads:[~2012-10-10 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 17:32 [xen-unstable test] 13944: regressions - FAIL xen.org
2012-10-09 18:00 ` Ian Jackson
2012-10-10 15:14   ` Dario Faggioli [this message]
2012-10-12 11:24     ` Ian Jackson

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=1349882083.3610.219.camel@Abyss \
    --to=raistlin.df@gmail.com \
    --cc=Ian.Jackson@eu.citrix.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.