From: Dylan Yudaken <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Kernel Team <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [PATCH liburing 6/7] test: add make targets for each test
Date: Fri, 22 Apr 2022 14:14:01 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 2022-04-22 at 20:40 +0700, Ammar Faizi wrote:
> On 4/22/22 6:48 PM, Dylan Yudaken wrote:
> > Add a make target runtests-parallel which can run tests in
> > parallel.
> > This is very useful to quickly run all the tests locally with
> > $ make -j runtests-parallel
> >
> > Signed-off-by: Dylan Yudaken <[email protected]>
>
> Two comments below...
>
> > test/Makefile | 10 +++++++++-
> > test/runtests-quiet.sh | 10 ++++++++++
> > 2 files changed, 19 insertions(+), 1 deletion(-)
> > create mode 100755 test/runtests-quiet.sh
>
> I suggest to add the following to the main Makefile:
> ```
> runtests-parallel: all
> +$(MAKE) -C test runtests-parallel
> ```
>
> So we can do this directly:
> ```
> make -j runtests-parallel;
> ```
> instead of doing this:
> ```
> cd test;
> make -j runtests-parallel;
> ```
>
> > -.PHONY: all install clean runtests runtests-loop
> > +%.run_test: %.t
> > + @./runtests-quiet.sh $<
> > +
> > +runtests-parallel: $(run_test_targets)
> > + @echo "All tests passed"
>
> Note that this parallel thing is doing:
>
> @./runtests-quiet.sh $THE_TEST_FILE
>
> ^ That thing is not a problem. But the ./runtests-quiet.sh exit code
> is.
> > diff --git a/test/runtests-quiet.sh b/test/runtests-quiet.sh
> > new file mode 100755
> > index 0000000..ba9fe2b
> > --- /dev/null
> > +++ b/test/runtests-quiet.sh
> > @@ -0,0 +1,10 @@
> > +#!/usr/bin/env bash
> > +
> > +TESTS=("$@")
> > +RESULT_FILE=$(mktemp)
> > +./runtests.sh "${TESTS[@]}" 2>&1 > $RESULT_FILE
> > +RET="$?"
> > +if [ "${RET}" -ne 0 ]; then
> > + cat $RESULT_FILE
> > +fi
> > +rm $RESULT_FILE
>
> This script's exit code doesn't necessarily represent the exit code
> of
> the `./runtests.sh "${TESTS[@]}"`, so you have to add `exit $RET` at
> the
> end of the script. Otherwise, the Makefile will always print "All
> tests
> passed" even if we have tests failed.
>
Both of these are good ideas - thanks! The second one especially is a
great spot. Will respin a v2 with them
Dylan
next prev parent reply other threads:[~2022-04-22 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 11:48 [PATCH liburing 0/7] run tests in parallel Dylan Yudaken
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 [this message]
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 \
--in-reply-to=b486973c0cfd475afd88763489bb5c1ef8c73f73.camel@fb.com \
[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