From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-test for v4.3 done
Date: Wed, 17 Feb 2016 10:15:56 +0800 [thread overview]
Message-ID: <56C3D7DC.2030403@oracle.com> (raw)
In-Reply-To: <20160216095411.GA8125@laptop.ha>
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.
Thanks,
Junxiao.
On 02/16/2016 05:54 PM, Eric Ren wrote:
> Hi Junxiao,
>
>>>> I have setup a test env to build and auto do ocfs2 test. With it, Ocfs2
>>>> for mainline and linux-next will be test regularly, the test status and
>>>> bugs will be reported to ocfs2-devel. Feel free to take any bug if you
>>>> are interested, it will be a good start point with ocfs2. Hope this can
>>>> catch regression bugs earlier before merged by mainline.
>>> I'm very interested in how your testing env works, could you briefly introduce
>>> it?
>> 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-17 2:15 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 [this message]
2016-02-19 3:01 ` Eric Ren
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=56C3D7DC.2030403@oracle.com \
--to=junxiao.bi@oracle.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).