From: Eric Sandeen <sandeen@sandeen.net>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 6/6] fsx: Add mechanism to replay failed operations
Date: Tue, 22 Dec 2015 16:35:59 -0600 [thread overview]
Message-ID: <5679D04F.6000803@sandeen.net> (raw)
In-Reply-To: <CAHc6FU5CsYbUJsUyWqWVfwY0OaiqOsy+BzxRS7dw5S+zfFJ+pw@mail.gmail.com>
On 12/22/15 4:12 PM, Andreas Gruenbacher wrote:
> On Tue, Dec 22, 2015 at 10:48 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> Can't we just leverage what fsx already provides? I'm not sure what this
>> patch adds on top of that, am I missing something?
>
> The -S and -D options help narrow down problems somewhat (xfstests
> always seems to use a constant seed value), but they don't allow
> removing unrelated operations in between or changing the order of
> operations. The .fsxops file makes that very easy; I've successfully
> used it on a gfs2 bug.
Now that you mention it, I guess I've done the same thing in the past
as well; I see the difference now. :)
-Eric
next prev parent reply other threads:[~2015-12-22 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 20:53 [PATCH 0/6] fsx Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 1/6] fsx: Small improvements and fixes Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 2/6] fsx: Fix hex numbers in operation dump Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 3/6] fsx: Report number of successful operations Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 4/6] fsx: Generate test parameters in test() Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 5/6] fsx: Improve operation logging Andreas Gruenbacher
2015-12-22 20:53 ` [PATCH 6/6] fsx: Add mechanism to replay failed operations Andreas Gruenbacher
2015-12-22 21:48 ` Eric Sandeen
2015-12-22 22:12 ` Andreas Gruenbacher
2015-12-22 22:35 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 13:51 [PATCH 0/6] fsx Andreas Gruenbacher
2015-12-22 13:51 ` [PATCH 6/6] fsx: Add mechanism to replay failed operations Andreas Gruenbacher
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=5679D04F.6000803@sandeen.net \
--to=sandeen@sandeen.net \
--cc=agruenba@redhat.com \
--cc=fstests@vger.kernel.org \
/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.