From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: linux-cr: ckpt-v23-rc2 pushed
Date: Sun, 17 Apr 2011 08:13:51 -0500 [thread overview]
Message-ID: <20110417131351.GA19709@hallyn.com> (raw)
In-Reply-To: <4DAA3B61.10504-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> Hi,
>
> I finally merged all the recent patches and bug fixes, including hugetlb
> and pids-as-objects. I pushed it as ckpt-v23-rc2 - both linux-cr and user-cr.
> It applies on top of 2.6.37.
>
> It passes all my testing here.
Do you have a checklist you can share?
> I'd be happy with more testing and for more
> architectures (PPC and ARM are still out until I receive updated patchsets).
>
> If you notice that I left out a patch/fix, please let me know.
>
> Thanks,
I'll kick off a build hopefully tonight.
Has anyone else had some thoughts on how to start on automated testing?
Should we take a look at jenkins? Does anyone have some hardware they
can dedicate? I think it would be a reasonable start to do crosscompile
builds for each support arch, with and without CR, and to fire off
qemu VMs for each arch just for a standard set of c/r tests (presumably
the ones under user-cr/tests) - and do that once per day. If it fails,
auto-fetch a list of commits since last success.
-serge
next prev parent reply other threads:[~2011-04-17 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 0:59 linux-cr: ckpt-v23-rc2 pushed Oren Laadan
[not found] ` <4DAA3B61.10504-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-04-17 13:13 ` Serge E. Hallyn [this message]
[not found] ` <20110417131351.GA19709-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2011-04-24 6:02 ` Oren Laadan
2011-04-18 13:35 ` Dan Smith
[not found] ` <87ipubptr1.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2011-04-24 5:47 ` Oren Laadan
2011-04-18 18:18 ` Matt Helsley
[not found] ` <20110418181803.GA3740-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2011-04-18 20:33 ` Serge Hallyn
2011-04-24 6:04 ` Oren Laadan
[not found] ` <4DB3BD53.40102-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-04-24 9:34 ` Oren Laadan
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=20110417131351.GA19709@hallyn.com \
--to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=orenl-eQaUEPhvms7ENvBUuze7eA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox