($INBOX_DIR/description missing)
 help / color / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <guan@eryu.me>
Cc: Eryu Guan <guaneryu@gmail.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Vivek Goyal <vgoyal@redhat.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 0/3] Running unionmount testsuite from xfstests
Date: Sun, 19 Jul 2020 21:36:39 +0300
Message-ID: <CAOQ4uxjY7SqyVEG9vCtv=wB9BxDovpjwZGAQ7h5+VeiZPMKOeQ@mail.gmail.com> (raw)
In-Reply-To: <20200719181116.GG2557159@desktop>

On Sun, Jul 19, 2020 at 9:11 PM Eryu Guan <guan@eryu.me> wrote:
>
> Hi Amir,
>
> 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.
> >
> > What does it take to install unionmount testsuite?
> > As README.overlay says:
> >
> >   git clone https://github.com/amir73il/unionmount-testsuite.git
> >   ln -s $PWD/unionmount-testsuite <path-to-xfstests>/src/
>
> I'm really sorry for the long-long delay..
>

No worries.

> The test itself looks really good to me, my only concern is that
> the updates in unionmount repo are not visible to fstests, and may cause
> new failures, which are out of fstests' control. But I'm not sure if
> this really is a problem for people.
>
> I came up with two options anyway
> - add unionmount tests as a submodule of fstests
> - put unionmount tests in fstests
>

I suppose you mean git submodule?
IMO that's a fairly good option.
I suspect that some people would want to continue running
unionmount independently of xfstests and I have some development
branches, so it's convenient to keep the unionmount repo independent
of xfstests repo and use git submodule as the "pull request" method
between us, for keeping control of the flow of changes from my repo
in the hands of xfstests maintainer.

But as I wrote before, I am also fine with "handing over" the official
upstream of unionmount src to xfstests project and be the
"sub-maintainer" for that module, but I think there is going to be more
chatter with that option compared to the submodule option.
Another argument in favor of submodule, is that we can always
graduate unionmount in the future from submodule to built-in.

Thanks,
Amir.

> I'd like to hear what people think about this patchset, any other
> comments & suggestions are welcomed!
>
> Thanks,
> Eryu
>
> >
> > Thanks,
> > Amir.
> >
> > Amir Goldstein (3):
> >   overlay: run unionmount testsuite test cases
> >   overlay: add unionmount tests with multi lower layers
> >   overlay: add unionmount tests with nested overlay
> >
> >  README.overlay        | 15 ++++++++++++
> >  common/config         |  2 ++
> >  common/overlay        | 54 +++++++++++++++++++++++++++++++++++++++++++
> >  tests/overlay/100     | 38 ++++++++++++++++++++++++++++++
> >  tests/overlay/100.out |  2 ++
> >  tests/overlay/101     | 39 +++++++++++++++++++++++++++++++
> >  tests/overlay/101.out |  2 ++
> >  tests/overlay/102     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/102.out |  2 ++
> >  tests/overlay/103     | 38 ++++++++++++++++++++++++++++++
> >  tests/overlay/103.out |  2 ++
> >  tests/overlay/104     | 39 +++++++++++++++++++++++++++++++
> >  tests/overlay/104.out |  2 ++
> >  tests/overlay/105     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/105.out |  2 ++
> >  tests/overlay/106     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/106.out |  2 ++
> >  tests/overlay/107     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/107.out |  2 ++
> >  tests/overlay/108     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/108.out |  2 ++
> >  tests/overlay/109     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/109.out |  2 ++
> >  tests/overlay/110     | 39 +++++++++++++++++++++++++++++++
> >  tests/overlay/110.out |  2 ++
> >  tests/overlay/111     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/111.out |  2 ++
> >  tests/overlay/112     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/112.out |  2 ++
> >  tests/overlay/113     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/113.out |  2 ++
> >  tests/overlay/114     | 39 +++++++++++++++++++++++++++++++
> >  tests/overlay/114.out |  2 ++
> >  tests/overlay/115     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/115.out |  2 ++
> >  tests/overlay/116     | 40 ++++++++++++++++++++++++++++++++
> >  tests/overlay/116.out |  2 ++
> >  tests/overlay/117     | 41 ++++++++++++++++++++++++++++++++
> >  tests/overlay/117.out |  2 ++
> >  tests/overlay/group   | 18 +++++++++++++++
> >  40 files changed, 843 insertions(+)
> >  create mode 100755 tests/overlay/100
> >  create mode 100644 tests/overlay/100.out
> >  create mode 100755 tests/overlay/101
> >  create mode 100644 tests/overlay/101.out
> >  create mode 100755 tests/overlay/102
> >  create mode 100644 tests/overlay/102.out
> >  create mode 100755 tests/overlay/103
> >  create mode 100644 tests/overlay/103.out
> >  create mode 100755 tests/overlay/104
> >  create mode 100644 tests/overlay/104.out
> >  create mode 100755 tests/overlay/105
> >  create mode 100644 tests/overlay/105.out
> >  create mode 100755 tests/overlay/106
> >  create mode 100644 tests/overlay/106.out
> >  create mode 100755 tests/overlay/107
> >  create mode 100644 tests/overlay/107.out
> >  create mode 100755 tests/overlay/108
> >  create mode 100644 tests/overlay/108.out
> >  create mode 100755 tests/overlay/109
> >  create mode 100644 tests/overlay/109.out
> >  create mode 100755 tests/overlay/110
> >  create mode 100644 tests/overlay/110.out
> >  create mode 100755 tests/overlay/111
> >  create mode 100644 tests/overlay/111.out
> >  create mode 100755 tests/overlay/112
> >  create mode 100644 tests/overlay/112.out
> >  create mode 100755 tests/overlay/113
> >  create mode 100644 tests/overlay/113.out
> >  create mode 100755 tests/overlay/114
> >  create mode 100644 tests/overlay/114.out
> >  create mode 100755 tests/overlay/115
> >  create mode 100644 tests/overlay/115.out
> >  create mode 100755 tests/overlay/116
> >  create mode 100644 tests/overlay/116.out
> >  create mode 100755 tests/overlay/117
> >  create mode 100644 tests/overlay/117.out
> >
> > --
> > 2.17.1
> >

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 11:01 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
2020-07-19 18:11 ` Eryu Guan
2020-07-19 18:36   ` Amir Goldstein [this message]
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='CAOQ4uxjY7SqyVEG9vCtv=wB9BxDovpjwZGAQ7h5+VeiZPMKOeQ@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --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

($INBOX_DIR/description missing)

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-unionfs/0 linux-unionfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-unionfs linux-unionfs/ https://lore.kernel.org/linux-unionfs \
		linux-unionfs@vger.kernel.org
	public-inbox-index linux-unionfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-unionfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git