From: Amir Goldstein <amir73il@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Eryu Guan <guaneryu@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 0/3] Running unionmount testsuite from xfstests
Date: Mon, 1 Jun 2020 22:18:44 +0300 [thread overview]
Message-ID: <CAOQ4uxhgeadCVKi-gzAuaiyyaVVPLc9yR-t5xkfUwAuCSSEDXQ@mail.gmail.com> (raw)
In-Reply-To: <20200601175219.GE3219@redhat.com>
On Mon, Jun 1, 2020 at 8:52 PM Vivek Goyal <vgoyal@redhat.com> wrote:
>
> On Sun, May 31, 2020 at 02:01:53PM +0300, Amir Goldstein wrote:
> > Eryu,
> >
> > unionmount testsuite has a lot more test coverage than the overlay
> > xfstests, but it has a lot less exposure to testers.
> >
> > The various test setups that I have added to unionmount testsuite since
> > I took over the maintanace of the testsuite have even smaller exposure
> > to testers.
> >
> > These patches add overlay tests that are used as a harness to run
> > different setups of unionmount testsuite. I have been using this method
> > for over two year for testing my overlayfs branches.
>
> Hi Amir,
>
> Is there a git branch somewhere with these changes. Its easier to pull
> that one in and test.
>
Of course. Forgot to mention.
https://github.com/amir73il/xfstests/commits/unionmount
Thanks,
Amir.
next prev parent reply other threads:[~2020-06-01 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 11:01 [PATCH 0/3] Running unionmount testsuite from xfstests Amir Goldstein
2020-05-31 11:01 ` [PATCH 1/3] overlay: run unionmount testsuite test cases Amir Goldstein
2020-05-31 11:01 ` [PATCH 2/3] overlay: add unionmount tests with multi lower layers Amir Goldstein
2020-05-31 11:01 ` [PATCH 3/3] overlay: add unionmount tests with nested overlay Amir Goldstein
2020-06-01 17:52 ` [PATCH 0/3] Running unionmount testsuite from xfstests Vivek Goyal
2020-06-01 19:18 ` Amir Goldstein [this message]
2020-07-19 18:11 ` Eryu Guan
2020-07-19 18:36 ` Amir Goldstein
2020-07-26 15:16 ` Eryu Guan
2020-07-26 16:21 ` Amir Goldstein
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=CAOQ4uxhgeadCVKi-gzAuaiyyaVVPLc9yR-t5xkfUwAuCSSEDXQ@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.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).