From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Pankaj Raghav <pankydev8@gmail.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Baseline for f2fs
Date: Tue, 19 Apr 2022 16:03:53 -0700 [thread overview]
Message-ID: <Yl8/2cPCkSZ17hxN@google.com> (raw)
In-Reply-To: <CAB=NE6W3r_O5L30pPLJ9s12ahfBGvudFAKyLbO_1=JCf2bDTkg@mail.gmail.com>
On 04/19, Luis Chamberlain wrote:
> On Tue, Apr 19, 2022 at 3:42 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > On 04/19, Luis Chamberlain wrote:
> > > I'm going to add automation support for f2fs within kdevops [0]. This
> > > should enable folks to test for regressions for f2fs from scratch with
> > > just a few commands. Before I go ahead and add that I was curious if
> > > folks have a known baseline of known failures from fstests for f2fs so
> > > I can expunge the known issues for now. Is there a tracker where these
> > > are kept as well?
> >
> > Well, I'm not sure what fstests will run. Is that based on xfstests?
>
> Yes. I call it fstests only because I'm tired of attending LSFMMs
> where folks don't realize that xfstests is used to test any
> filesystem. So I figured we need to rebrand it.
I see. This is what I modified a bit based on xfstests for f2fs.
https://github.com/jaegeuk/xfstests-f2fs/commits/f2fs
Thanks,
>
> Luis
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-04-19 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:21 [f2fs-dev] Baseline for f2fs Luis Chamberlain
2022-04-19 22:41 ` Jaegeuk Kim
2022-04-19 22:42 ` Luis Chamberlain
2022-04-19 23:03 ` Jaegeuk Kim [this message]
2022-04-19 23:26 ` Luis Chamberlain
2022-04-20 4:02 ` Luis Chamberlain
2022-04-20 18:12 ` Jaegeuk Kim
2022-04-20 18:23 ` Luis Chamberlain
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=Yl8/2cPCkSZ17hxN@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=mcgrof@kernel.org \
--cc=pankydev8@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.