From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: OOM panics in the test suite
Date: Sat, 20 Jun 2009 09:00:49 +0200 [thread overview]
Message-ID: <4A3C8921.4060406@redhat.com> (raw)
In-Reply-To: <1245444788.19114.2.camel-FqX9LgGZnHWDB2HL1qBt2PIbXMQ5te18@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
Am 19.06.2009 22:53, schrieb David Dillow:
> Commit 3af5866 "use 128M for the test virtual machines instead of 512M"
> now causes all of the test suites to panic with the OOM killer when run
> under F10 -- 256M seems to work better.
>
> Does it work for anyone under F11 or Debian?
>
> Is there an objection to moving it to 256M instead?
No, do it! I was just thinking that we should not need 512M. And on F11 it runs fine with 128M.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3636 bytes --]
prev parent reply other threads:[~2009-06-20 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 20:53 OOM panics in the test suite David Dillow
[not found] ` <1245444788.19114.2.camel-FqX9LgGZnHWDB2HL1qBt2PIbXMQ5te18@public.gmane.org>
2009-06-20 7:00 ` Harald Hoyer [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=4A3C8921.4060406@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.
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.