From: vincentfu@gmail.com
To: axboe@kernel.dk, fio@vger.kernel.org
Cc: Vincent Fu <vincent.fu@wdc.com>
Subject: [PATCH 0/9] testing patches
Date: Tue, 10 Dec 2019 12:54:33 -0500 [thread overview]
Message-ID: <20191210175442.2975-1-vincentfu@gmail.com> (raw)
From: Vincent Fu <vincent.fu@wdc.com>
Jens, please consider this series of patches related to testing.
The patches improve t/run-fio-tests.py in various ways, most prominently
adding support for Windows and macOS.
Also included are travis and appveyor patches that add run-fio-tests.py
as a step. Currently both the travis and appveyor build processes
complete in less than four minutes. Adding run-fio-tests.py increases
this to about 20 minutes for travis and 14 minutes for appveyor.
Also worth noting is that sometimes the VMs these builds run on appear
to become overloaded and produce false failures. For instance, builds on
the same hash fail here
https://ci.appveyor.com/project/vincentkfu/fio/builds/29342164
but succeed here
https://ci.appveyor.com/project/vincentkfu/fio/builds/29344271
The failure occured because of a timeout running a null ioengine job that
reads 10G of data.
It's certainly nice to have these tests automatically run with every
commit, but the downside is that the build process is significantly
lengthened and some noise is introduced.
Vincent Fu (9):
.gitignore: ignore zbd test output files
t/run-fio-tests: a few small improvements
t/run-fio-tests: detect requirements and skip tests accordingly
t/run-fio-tests: improve Windows support
t/run-fio-tests: identify test id for debug messages
t/steadystate_tests: use null ioengine for tests
.travis.yml: run t/run-fio.tests.py as part of build
.appveyor.yml: run run-fio-tests.py
t/run-fio-tests: relax acceptance criterion for t0011
.appveyor.yml | 6 +-
.gitignore | 1 +
.travis.yml | 26 ++---
t/run-fio-tests.py | 219 ++++++++++++++++++++++++++++++++++++-----
t/steadystate_tests.py | 21 +---
5 files changed, 219 insertions(+), 54 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-10 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 17:54 vincentfu [this message]
2019-12-10 17:54 ` [PATCH 1/9] .gitignore: ignore zbd test output files vincentfu
2019-12-10 17:54 ` [PATCH 2/9] t/run-fio-tests: a few small improvements vincentfu
2019-12-10 17:54 ` [PATCH 3/9] t/run-fio-tests: detect requirements and skip tests accordingly vincentfu
2019-12-10 17:54 ` [PATCH 4/9] t/run-fio-tests: improve Windows support vincentfu
2019-12-10 17:54 ` [PATCH 5/9] t/run-fio-tests: identify test id for debug messages vincentfu
2019-12-10 17:54 ` [PATCH 6/9] t/steadystate_tests: use null ioengine for tests vincentfu
2019-12-10 17:54 ` [PATCH 7/9] .travis.yml: run t/run-fio.tests.py as part of build vincentfu
2019-12-10 17:54 ` [PATCH 8/9] .appveyor.yml: run run-fio-tests.py vincentfu
2019-12-10 17:54 ` [PATCH 9/9] t/run-fio-tests: relax acceptance criterion for t0011 vincentfu
2019-12-10 21:32 ` [PATCH 0/9] testing patches Sitsofe Wheeler
2019-12-11 19:53 ` Vincent Fu
2019-12-11 19:57 ` Jens Axboe
2019-12-11 20:10 ` Vincent Fu
2019-12-12 3:54 ` Jens Axboe
2019-12-12 8:37 ` Sitsofe Wheeler
2019-12-16 22:13 ` Jens Axboe
2019-12-16 22:42 ` Vincent Fu
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=20191210175442.2975-1-vincentfu@gmail.com \
--to=vincentfu@gmail.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=vincent.fu@wdc.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