public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xfstests and (automated) workflow?
@ 2017-03-06 14:25 Jan Tulak
  2017-03-06 21:51 ` Dave Chinner
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Tulak @ 2017-03-06 14:25 UTC (permalink / raw)
  To: linux-xfs

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?

Thanks,
Jan

-- 
Jan Tulak
jtulak@redhat.com / jan@tulak.me

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-07 17:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-06 14:25 xfstests and (automated) workflow? Jan Tulak
2017-03-06 21:51 ` Dave Chinner
2017-03-07  8:04   ` Jan Tulak

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox