From: Dave Chinner <david@fromorbit.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfstests and (automated) workflow?
Date: Tue, 7 Mar 2017 08:51:12 +1100 [thread overview]
Message-ID: <20170306215112.GN17542@dastard> (raw)
In-Reply-To: <CACj3i72avXdkrQdfGnfeRpnOoPo+bcBMForczMt_dnK-ZXQbkg@mail.gmail.com>
On Mon, Mar 06, 2017 at 03:25:03PM +0100, Jan Tulak wrote:
> Hi guys,
>
> II decided to streamline and automate some things for me with testing
> xfs, but as I worked on it, I realise that surely I'm not the first
> one to do that. So I would like to ask you, can you share your tips
> and tricks? :-)
>
> What I began to work at is a small suite of scripts to deploy a docker
> container (could be changed for a VM) which compiles my local version
> of xfsprogs and xfstests, runs it, and if I specify multiple
> revisions, it does it for every of the revisions and then tells me
> which test results changed between the revisions. I know the
> comparison of failures between runs can be done with
> tools/compare-failures. It doesn't detect a change in "not run"
> though, which I would like to detect too.
>
> Are you using anything like this you can share?
Ted's xfstests-bld does this sort of stuff, IIRC, using KVM:
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-03-06 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:25 xfstests and (automated) workflow? Jan Tulak
2017-03-06 21:51 ` Dave Chinner [this message]
2017-03-07 8:04 ` Jan Tulak
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=20170306215112.GN17542@dastard \
--to=david@fromorbit.com \
--cc=jtulak@redhat.com \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox