From: Vincent Fu <vincentfu@gmail.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: testing roadmap for fio
Date: Mon, 11 Nov 2019 11:43:48 -0500 [thread overview]
Message-ID: <03e1f4a5-dfce-e856-ac18-0832d2e383ce@gmail.com> (raw)
I would like to undertake an effort to contribute more regression tests
to fio.
My initial thought is to add more jobs to t/jobs. Unlike the jobs
currently there, these new jobs would not target specific bugs. Instead,
the jobs would exercise a variety of fio's options and use
run-fio-tests.py to examine the JSON output to confirm that the options
specified were appropriately respected.
Does this sound like a reasonable approach? Are there better directions
to focus my efforts?
Vincent
reply other threads:[~2019-11-11 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=03e1f4a5-dfce-e856-ac18-0832d2e383ce@gmail.com \
--to=vincentfu@gmail.com \
--cc=fio@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