From: Eric Ren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-test for v4.3 done
Date: Fri, 19 Feb 2016 11:01:24 +0800 [thread overview]
Message-ID: <20160219030124.GA4861@laptop.ha> (raw)
In-Reply-To: <56C3D7DC.2030403@oracle.com>
Hi Junxiao,
On Wed, Feb 17, 2016 at 10:15:56AM +0800, Junxiao Bi wrote:
> Hi Eric,
>
> I remember i described it before, please search it on ocfs2-devel. For
> ocfs2 env setup, please refer to README in ocfs2-test.
Yes, you did. Actually, it's the quoted paragraph below;-)
Thanks, but more things what I really want to learn about are, such as:
1. git hook/auto control scripts, if it's OK to share;
2. pain point and solution, for example, a latest tagged release kernel may
not compile successfully by `make defconfig` or `cp /boot/config-`uname -r``;
Or cannot boot up even if we've built kernel RPM and installed it.
Did you have this problem? Any suggestion;-) What I can think of is to try opensuse
tumbleweed distribution(a rolling release).
>
> On 02/16/2016 05:54 PM, Eric Ren wrote:
> > Hi Junxiao,
> >
> >> Four vm are used, one for git server, and the other three to build
> >> kernel and run ocfs2 test. Tag a branch and push it to the git server,
> >> the test will be started. The test cases to run can be set in tag message.
> >
> > Recently, I get free days and also want to setup automatic testing env for ocfs2.
> > I'll use pcmk as cluster stack while you probably use o2cb. I think we can complement
> > each other. May I bother you to describe the work flow more specifically, or share
> > experiences and references? That way it would save my life;-)
> >
Thanks!
Eric
next prev parent reply other threads:[~2016-02-19 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 3:00 [Ocfs2-devel] ocfs2-test for v4.3 done Junxiao Bi
2015-12-21 13:50 ` Eric Ren
2015-12-22 2:34 ` Junxiao Bi
2015-12-22 7:39 ` Eric Ren
2016-02-16 9:54 ` Eric Ren
2016-02-17 2:15 ` Junxiao Bi
2016-02-19 3:01 ` Eric Ren [this message]
2016-02-24 1:48 ` Junxiao Bi
2016-02-24 3:30 ` Eric Ren
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=20160219030124.GA4861@laptop.ha \
--to=zren@suse.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).