From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: ebiggers@google.com, enwlinux@gmail.com, leah.rumancik@gmail.com,
harshadshirwadkar@gmail.com
Subject: Directory reorganization in xfstests-bld pushed out
Date: Tue, 24 May 2022 09:52:26 -0400 [thread overview]
Message-ID: <YozjGjNv9dEW/m0L@mit.edu> (raw)
I've justed pushed out a change to the xfstests-bld directory which is
especially disruptive for people who are building test appliances
using xfstests-bld.
The directory structure in xfstests-bld reflects its original design
as a hermetic build system for xfstests. However, these days, its
primary focus is the an test appliance featuring xfstests (but these
days, we also support blktests the Phoronix test suite, etc.) and
drivers to run the test appliance on a variety of environments ---
e.g., kvm-xfstests, gce-xfstests, and android-xfstests.
To make life easier for new users of xfstests-bld, especially who want
to use kvm-xfstests, I've reorganized the directory structure and
moved around files and directories so they are sorted into four
top-level directories:
fstests-bld The hermetic build system for xfstests
test-appliance The test runner infrastructure for xfstests (and blktests
and Phoronix Test Suite....)
run-fstests The test runner command line utilities, namely kvm-xfstests,
gce-xfstests, etc.
build-kernel Utilities to build and configure the Linux kernel in a
standard way which is easy for the test runners to run.
There is a script in fstests-bld/misc/post-reorg-cleanup which may be
helpful in moving the external repos and other files to the proper
places after this reorganization. Please take a look at it before
running it, and I recommend that you use the --no-action option first.
Since the most developers will only need to run the script once, it
may be a little rough, and it does delete some files and directories.
- Ted
next reply other threads:[~2022-05-24 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:52 Theodore Ts'o [this message]
2022-05-24 19:26 ` Directory reorganization in xfstests-bld pushed out Eric Biggers
2022-05-26 18:06 ` Theodore Ts'o
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=YozjGjNv9dEW/m0L@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@google.com \
--cc=enwlinux@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=harshadshirwadkar@gmail.com \
--cc=leah.rumancik@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox