From: Dylan Yudaken <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
Dylan Yudaken <[email protected]>
Subject: [PATCH liburing 0/7] run tests in parallel
Date: Fri, 22 Apr 2022 04:48:08 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This series allows tests to be run in parallel, which speeds up
iterating. Rather than build this functionality into the shell scripts, it
seemed much easier to use make's parallel execution to do this.
My bash/make skills are not top notch, so I might have missed something
obvious, however it does seem to work locally very nicely.
Patch #1 is a bug that seems to trigger quite often when running in parallel
Patch #2-5 fix bugs that prevent tests running in parallel
Patch #6 adds a make target that depends on running each test
Patch #7 Is not related to parallel tests. It is a prep for a later series to use nop to test IOPOLL.
Dylan Yudaken (7):
test: handle mmap return failures in pollfree test
test: use unique path for socket
test: use unique ports
test: use unique filenames
test: mkdir -p output folder
test: add make targets for each test
test: use remove_buffers instead of nop to generate error codes
test/232c93d07b74.c | 2 +-
test/Makefile | 10 +++++++++-
test/accept-test.c | 2 +-
test/defer.c | 28 ++++++++++++++++++++--------
test/link.c | 6 +++---
test/openat2.c | 6 +++---
test/pollfree.c | 4 ++--
test/recv-msgall.c | 2 +-
test/runtests-quiet.sh | 10 ++++++++++
test/runtests.sh | 2 +-
test/send_recv.c | 2 +-
test/send_recvmsg.c | 2 +-
test/sq-poll-dup.c | 2 +-
test/sq-poll-share.c | 2 +-
14 files changed, 55 insertions(+), 25 deletions(-)
create mode 100755 test/runtests-quiet.sh
base-commit: b7d8dd8bbf5b8550c8a0c1ed70431cd8050709f0
--
2.30.2
next reply other threads:[~2022-04-22 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 11:48 Dylan Yudaken [this message]
2022-04-22 11:48 ` [PATCH liburing 1/7] test: handle mmap return failures in pollfree test Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 2/7] test: use unique path for socket Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 3/7] test: use unique ports Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 4/7] test: use unique filenames Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 5/7] test: mkdir -p output folder Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 6/7] test: add make targets for each test Dylan Yudaken
2022-04-22 13:40 ` Ammar Faizi
2022-04-22 14:14 ` Dylan Yudaken
2022-04-22 11:48 ` [PATCH liburing 7/7] test: use remove_buffers instead of nop to generate error codes Dylan Yudaken
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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